Add Test Commands for each subsystem.

[devinvs]

Since we have had difficulties getting each subsystem to send its stats to shuffleboard, I want to create commands that will give us full control over a subsystem while monitoring all of its stats. To start, each command should open a new tab named after the subsystem it controls and monitors. All motor outputs should come from shuffleboard just as if we were changing them in a command. If we are going to use the subsystem in multiple "modes" (like PID control), let us change constants and the "mode" the motors are running in just as we will in other commands. For every motor, output motor position, velocity, and current, each as its own separate graph. Please also output relevant sensor information or states that would affect our usage of that subsystem. Once this is finished, it will give us a quick way to find mechanical flaws without endless searches through the code. There is a lot here, so feel free to come to me with questions. Finally, DO NOT TRY TO DO ALL OF THE COMMANDS IN ONE PULL REQUEST. If possible, I want multiple people working on this issue at once, so choose one and only one subsystem to work on and comment that you are taking it below.

[StephenDay1]

I will try to start working on this, starting with the shooter.

[aeroplaneb29]

I will work on intake test