migrate to "framework-based" style

[yehpop]

unsure if framework-based would be a correct name. i want to keep subsystems of team nf robots scripted in a library type repository and import from that repository when coding the robot code for the regionals.

[yehpop]

trying to find examples or references to go by, team100/main2023, team254 com.team254.lib ???

[yehpop]

should the "framework" or "library" include only extensions on wpilib with abstract systems; including only drivers, geometry, util classes etc. such as the team254 lib or shall i write it as a kind of toolbox that stores everything needed for any frc robot the team may make. If the latter than the subsystems written for any robot will be added to this "framework" so it may be imported and used again. New subsystems and former ones will be defined and written in this framework and not in the robot's own code. Subsystems may be more abstract here or both abstract and detailed versions may be present. Not sure how to implement this idea...