Path switcher w/ "section"-based path switching

[jbko6]

Last year, I created our autonomous chooser system. Which was nice, and should be replicated this year. However, there are some reasons to believe that just an auto chooser where you just choose the entire auto at once might not cut it. With so many potential paths for the robot to go, there's not many easy ways to predict just how our alliance members are going to code their own paths. The worst thing would be for us to have no path possible because alliance member's paths conflict with ours.

So, we use a "section"-based path switcher this year (name suggestions welcome). Instead of choosing the entire auto all at once, you break the autos up into little sections. Each auto has, say, 3 sections, and instead of picking the auto, you pick which section fits in for the beginning, middle, and end! This way, the drive team can sort of "build" out the path as they are discussing with alliance members.

Here's what's needed for this to be effective:

• Some sort of way to blend the sections together, whether that be having the beginning/middle sections end/start in the same spot, or some other way of getting the robot to the next section
• A visualization of their built path for drive team. Last year I experimented with using this team's library https://github.com/Arctos6135/StdPlug for displaying images in shuffleboard. It might be interesting to try and build my own widget for shuffleboard this year.
• We'll still need a lot of variety in what sections are offered

At the end of the day, this will be a "nice to have" feature. We should focus on getting everything else working before starting on this.