LIMS-753: Allow LN2 topups as part of dewar history

[ndg63276]

JIRA ticket: LIMS-753

Summary:

We record every time a dewar is topped up with LN2, but in the Dewar.comments field. In order to let the users know what has happened to their dewar, we should record it in the DewarTransportHistory table.
Once this code is live, I can edit the Dewar Logistics code to use this endpoint instead.

Changes:

• Allow usage of the shipments/dewars/history endpoint with a STATUS instead of a LOCATION.
• Update only DewarTransportHistory (and not Dewar) if only STATUS given
• Only send emails if the location has changed (and other criteria met)

To test:

• Edit the $bcr variable in config.php to include the IP of a machine you can ping your server from
• Use python requests library (or similar) to hit the endpoint:

>>> import requests
>>> url = server_address + "/api/shipment/dewars/history"
>>> data = {"BARCODE": valid_dewar_barcode, "STATUS": "LN2 topped up"}
>>> r = requests.post(url, json=data)

If you get a 401 response, double check the $bcr variable. If you get a 200, go the dewar page on your Synchweb instance and check if the status has been added to the history. If no history shows, you might need to remove your IP from $bcr, it can get in the way. It should look like this:

• Repeat the test with a LOCATION sent in instead of STATUS. Check the dewar location has changed in both the Dewar and DewarTransportHistory tables.