Re-implement logging #32
Description
I took this out a while ago because it didn't seem to be used very much in practice. However, I think there should be a way to debug other issues like problems with a fridge or an instrument. Example situation:
Whenever user A uses the magnet, there is a magnet quench, but A does not know what causes it and it seemingly occurs at random times.
The issue that labdrivers could hopefully answer in the future is this: using data, how could you troubleshoot when exactly it happens?
The answer could be, for example, this only occurs when the temperature is in a certain range, or maybe there's a pressure in the dil fridge that, for whatever reason, causes the magnet to quench. In addition to logging data directly relevant to the experiment, how do we gather other data about the state of the experimental apparatus?