Initial pre-implementation cleanup

[aidnem]

This PR fixes #18 Purpose The purpose of this addition is to make sure the repository is structured well and isn't too janky before we start adding more specific/advanced features to subsystems.

Project Scope

• [x] Gitignore src/main/java/frc/robot/BuildConstants.java
• [x] Make drivetrain controlled by a feature flag
• [x] Make scoring + intake controlled by a feature flag
• [x] Make sure constants are in the right place
• [x] Make sure subsystems and commands are all in the right folders
• [x] Make RobotContainer structured + ordered correctly
• [x] (after shooter/intake is merged) make sure subsystems play nice in sim and work together without issue.

[aidnem]

@jkleiber I have a code style question: In 2024 we created the CommandSwerveDrivetrain in the tuner constants, and then used a ternary to choose whether or not to assign it in RobotContainer. For high-key I changed this to only create the drivetrain if drive is enabled, but this meant I had to make all of the parameters for drive public so that they could be imported into robot container. Do you have a preference either way on this? I lean towards not instantiating it unless we need it, but I'm open to changing my mind.

[jkleiber]

@aidnem I think the concept of "don't instantiate what you aren't using" makes sense. I'm not sure why you would need to make things public though

[aidnem]

I've fixed the change so I'm going to branch off of here to start integration today since it's the closest we have to a good starting point.

[aidnem]

@jkleiber not sure if you saw during your time away, but we're currently under a boil water advisory, make sure you boil tap water before drinking it or drink bottled water. Figured I'd let you know just in case you didn't get notified while you were away.

[jkleiber]

@aidnem thanks for the heads up - I was aware due to various email updates but better to be safe than sorry 🫡