Make Custom Robot Class

[CodeMyGame1]

Problem: Although there will be separate class files for the different subsystems on the official High Stakes robot, the code is directly interacting with different VEX components (PROS classes) on a relatively low level

Significance: It would be much easier if all classes are condensed into a single wrapper class—Robot—that also serves as an interface between our code and the LemLib chassis

Solution: I propose creating a new file in include—robot.cpp (along with the corresponding robot.hpp file)—that brings together and automatically initializes all the different subsystems, given port numbers and other configuration values. It will then...

• provide an abstraction between our code and the LemLib chassis
• allow all subsystems to be accessed from one "place"

[CodeMyGame1]

In addition, it would be nice if the Robot class can abstract all code run in opcontrol() into a singular "main loop" type function, that can then be called in opcontrol() as its one and only line of code

[CodeMyGame1]

Also, add the CLI tuning class (expanded on in gh-3) as a class attribute of the Robot class, so an instance of the Robot class can be used to run CLI functions like detecting input and displaying certain things to the dashboard!