Avoid using the CameraServer and have the driver station directly use the webcam's server

[rhauch]

The CameraServer uses 2 threads internally, and that bogs down the RoboRIO as evidenced by lots of the following error messages in the log:

ERROR: Unable to execute all activities within XX milliseconds!

Have we tried setting up the camera as a webcam and having the DriverStation directly talk to it over the network? That would keep the RoboRIO completely out of the loop for all vision-related things, and would dramatically lower the compute load currently placed on the RoboRIO via CameraServer.