Revert remove prior array changes

[enjuthulung]

Summary:

• Reverted remove prior array commit from Put original_value for skipping write_value extra calculation #19

[RaiBnod]

Scenario:

The older LoRa point has maintained the priority array. And in the newer one after this commit, it's directly updating the values.

In our point write flow, if priority_array is there it takes the first priority as in here.

As a result, when we edit the LoRa point, the priority_array values get populated in original_value and so in present_value.

So, the fix would be to either keep that priority_array or remove that priority_array completely from LoRa.

Let's keep that priority_array _16.

@Shiny380 do you have any issue maintaining that priority_array 16?

[Shiny380]

nah I don't care how it's implemented. worth noting that the priority array is irrelevant to lora so whatever is the simplest fix :)
please make sure it's tested before merging. use a controller in the office