Sequencing redesign (UI mockups, etc.)

Core features:

[x] Better sequence format ("close eth vent, wait 15.0s, download svg" instead of the current scheme).
- [x] If the sequence starts in a state where a the sequence will attempt an illegal action depending on whether the start state has a pin on or off, we need to be careful. Currently our abort sequence interrupt may fail if valves are in the wrong configuration. I think instead of not being able to turn on vent when pressurisation is on, turning on vent should turn off pressurisation
[x] Store on the server, edit inline in the front-end interface (this way we don't accidentally upload out of date sequences)
- [x] The abort sequence should be specially marked
- Need mockups of the sequence editing interface: perhaps a modal dialog with a textarea? (decided not to make them editable inline)
[x] Remove pin numbers from the control panel panel now that they're not used in the sequence format
Cancelling, resetting and pausing sequences
[x] Port current sequences to the new format, and potentially make the sequence save folder in the git repo
[x] Revisit the server's sequencing code: it's quite complex async code. If we can simplify it and thoroughly test it, that would be great (we'll need to be careful of things like comparing epoch times from different computers and interrupting sleep commands with aborts/resets/cancels)

Other notes

[x] Test the rebuilt sequences in the next test
Automatic data capture will be integral for the next few tests. Auto download CSV with time, data columns over the interval (#2)
Use consistent datalogging formats for the client and server (CSV for high resolution data per #1 and CSV for pin firings). Test thoroughly that these datalogging CSV files are always generated (eg should work if logs folder doesn't already exist, should be enabled by default in live mode and disabled by default in development/fake labjack mode)
Heavy manual testing before the next test

ANU-Rocketry / control-panel