Rewite how motors are controlled and declared

[RED-M0CKING-LINE]

Summary:
At the moment we interface directly with the motor's API with no control of how the motor is declared, handled, or removed. This will also interface with the encoder classes to declare and handle the encoder by passing arguments through the declaration of each motor.
THIS MUST BE COMPLETED AFTER THE IMPLEMENTATION OF THE FEATURE IN ISSUE #2

Goal:
Make a dynamic class for each type of motor that allows easy declaration, control, and easy access to it is assigned or defined encoder.
Also, allow the class to return whether the motor is connected or not and if it is not, do not initialize whatever subsystem it belongs to and print a message that says: "____________ subsystem was not loaded due to motor ____________ being disconnected." This will require heavy testing of all the different motors and will need to be checked for reliability in detecting the presence of a motor controller.

Note:
If the above feature is not possible (any part of it), state here that it was not or cannot be completed, push the commits that implement this feature that also say this issue is now closed, and close this issue.