Results after Shooter Testing

[JohnGilb]

Why are we doing this?

The robot is mostly feature-complete; these are mostly small changes needed to operate the machine for testing, particularly shooter testing.
Asana task URL:

Whats changing?

• Renames of some important position enums
• Organizing operator controls into a "basic" and "advanced" gamepad. Basic for simple/emergency operations, advanced for 1-button solutions.
• Changing most motors to Coast when idle. For the Arm, this is to support manually moving it after a match. For others, it's to allow mechanical a better sense of how much native resistance there is in the system.
• Moving away from "angle" in the arm and using only "millimeters of extension" for now, as it's very easy to measure.
• Added data from testing the real shooter against the speaker.

Questions/notes for reviewers

How this was tested

• unit tests added
• tested on robot