Additional API interfaces and implementations


	
This should get us up to speed on most of the API stuff, in this PR we've got interfaces and implementations for: 
* Motors 
* Gyroscopes 
* Distance Sensors 
 
The only thing missing from last years robot is the accelerometer 
 
It also adds the `LimitedMotor` composite class and JUnit test cases, which though similar in concept to `SolenoidWithPostion`, isn't worth trying to abstract. 
 
Aside from that I fixed some documentation and refactored Hardware so that similar factory methods are in nested classes. 
 
Some things that might be worth considering: 
* The `Hardware` and `Mock` prefixes are a little overkill, the names are different enough to prevent conflicts, and if not, they're in separate packages. 
* If we are going to rely on the accelerometer and gyroscope more heavily then last year, it might be beneficial to have some helper classes that allow us to attach units and direction to a value, e.g. `Angle`, `Velocity`, `Displacement`, etc. 
Maybe we shouldn't even clamp it here, if we are giving it a value outside of [-1.0, 1.0], then we have a logic error somewhere else, clamping it would only hide the issue.  That being said, we still do want to validate it, maybe even throw an exception if it is out of bounds.

The difficulty with the name is that the watch dog prevents us from moving the motor with only one call to the command, so a name that implies an instantaneous action doesn't make sense.  I suppose `set` is moving wrong direction, I was going more for `setTarget...`, but I don't like that either. Maybe `moveTowards...`?