Transition shooter to state machine

[i-am-gizm0]

Along with #73, to help avoid problems with multiple methods attempting to control the motor at once, the shooter should behave like a state machine and either update its state when methods are called (which wouldn't do much for preventing control collisions but could clear things up a bit) or require defining what state it should be in before calling it (it would throw an exception when you didn't).