Better standard output piping between rust and python components

[JaminMartin]

Currently the Rust CLI only returns the standard output from python once the python script has completed. This should be able to be fixed. This is not a major issue, and is more of an enhancement. This allows for a degree of debugging if completed. However it would be better if the Rust based experiment manager handled this with logging, and also that it handled ALL of the data processing async from the experiment ensuring the measurements are more fault tolerant.

[JaminMartin]

Can use a TCP socket to pipe data back to the rust CLI, this will allow all processing and recording to happen in Rust.

• The "experiment" connects as a handler, this will enable sending pause, start stop signals to the python script.
• Each equipment connects to the socket and streams data.
• Rust parses the data into a struct that can be more easily written into the output log file

[JaminMartin]

As of e1cb269, TCP server & one way day exchange is implemented and has been tested with both fake and real instruments.

Need to implement pause, continue, stop etc interrupts for finer instrument control.