Create a telemetry client.

Nobody has claimed this yet.

The Socket Architecture already works over abstract network interfaces (I tested it on UCB Wireless). With some exceptions including firewalls (I doubt eduroam will work) the entire framework works remotely as long as you stay on the same network. Now, I would like to have a client to be able to upload modules onto the robot, monitor robot stats etc.

# Telemetry Client:
A Telemetry client is an endpoint for the user. This can mean testing, or telemetry control of the robot from a remote client.

# Description of the work.
Create a control client, required for the user's computer, that would allow you to monitor the open sockets on the robot. We need to open another channel that can be dynamically opened / closed, and allow for dynamic configuration of the robot.

Start by reading the existing Socket Architecture and its abstract network interfaces, then trace how the robot's open sockets are represented. Define the telemetry client's monitoring, upload, dynamic channel, and robot-configuration requirements before implementing them; done means a remote user can perform those operations reliably.

Written by the indexing model from the issue text.