Full web GUI integration

[Terracom12]

Fully integrate all systems to be used with the web GUI. This means that all behaviors and functionalities previously present through CLI, should be runnable / observable in the GUI.

An overview of some necessary steps:

In the GUI:

• Build a system to launch (arbitrary?) nodes. Ensure that error handling is done properly.
• Keep track of and allow the user to view logs. A filtering per-node system would be nice as well.

Other repos:

• SaddlebackCollegeRobotics/.github-private#132 so that the web GUI can monitor and display logs and possibly diagnostics

[Terracom12]

The systems repository would be a great place to start for how each subsystem is launched and run.

• Better documentation for subsystem actions and configuration

[Terracom12]

@RyanDewey
A summary of functionalities that should be readily available on the GUI:

Subsystem launch buttons. This includes the following:

• Drive (Local control input and rover motor controller)
• Arm (Local control input and rover motor controller)
• GPS (Local base GPS for correction and rover GPS launch)
• Televideo (Local video decoders and rover video encode and transmit)
• Autonomy (WIP; Probably will be a single launch on the rover)
• Science (WIP; Last year's system had a local node for sending commands, and one remote node to receive and relay to the microcontroller)

Per-mission launch buttons. This includes the following, each launching the parenthesized nodes:

• Delivery Mission (Drive, Arm, GPS, Televideo)
• Equipment Servicing Mission (Drive, Arm, GPS, Televideo, Autonomous arm system TBD)
• Science Mission (Drive, GPS, Science, Televideo)
• Autonomy Mission (Drive, GPS, Televideo, Autonomy)