FROST server ids sometimes do not match the self link

[C-Loftus]

• all observation posts succeed
• there are no duplicates detected by the db or in my tests
• despite this, the value of the iot.id selfLink appears different from the iot.id value in the json.
  • it seems like it lags behind one or two values for some reason
  • i don't have any logic that adds or subtracts from previous iot.id values. the iot.id is just being generated by concatting the according to the logic in new iotid generation strategy #25

You can see that 14010000019030204 appears duplicated shows up twice in the iot.id field but despite this it doesnt affect appear duplicated if you try to filter by it. The underlying iot.id inside the db appears to be unique. This is moreso a json encoding issue on FROST's end it seems

However if you filter by that particular iot.id that appears to be duplicated 14010000019030204, only one value appears so it is something incorrect it seems inside FROST.

[C-Loftus]

I have added tests for this inside the dag and it doesnt error out in ci/cd but it seems to be an issue still here: https://owdp-pilot.internetofwater.app/FROST-Server/v1.1/Observations

Seems to be something with either scale or caching since there are no other differences on the server vs local