Add Robot Spawn Positions [AARD-2041]

[rutmanz]

Task

AARD-2041

Symptom

Currently robots spawn at the center of the field (2018 is particularly annoying here) and have no defined starting places for match mode. This means that they will start wherever they were last sitting before match mode started, which isn't necessarily what you want

This will be particularly important for multiplayer games where you have several robots to deal with

Solution

Adds default spawn positions for each driver station to the devtools interface and allows them to be configured through there. I have configured default positions for the 2018 field and updated the assetpack

Verification

1. Run bun assetpack
2. Spawn 2018 field v13
3. Spawn Dozer (and notice that it isn't inside a wall)
4. Start match mode and check the "Move Robots to Starting Positions" checkbox
5. Observe how your robot moved to that spot

---

Before merging, ensure the following criteria are met:

• All acceptance criteria outlined in the ticket are met.
• Necessary test cases have been added and updated.
• A feature toggle or safe disable path has been added (if applicable).
• User-facing polish:
  • Ask: "Is this ready-looking?"
• Cross-linking between Jira and GitHub:
  • PR links to the relevant Jira issue.
  • Jira ticket has a comment referencing this PR.

[ryanzhangofficial]

When I spawn two 2024 kitbots and 2024 field and start matchmode with the toggle on and different driver stations, they both snap to the center of the field and are on top of each other.

[rutmanz]

@ryanzhangofficial This is because that field doesn't have actual points configured (I've only done 2018), but I changed the defaults so that they won't overlap anymore

I can create default spawn points for all of the fields but it might make more sense as a separate ticket (thoughts?)

[AlexD717]

lgtm

Can this new FRC field be added to where our current fields are hosted?

[ryanzhangofficial]

@ryanzhangofficial This is because that field doesn't have actual points configured (I've only done 2018), but I changed the defaults so that they won't overlap anymore

I can create default spawn points for all of the fields but it might make more sense as a separate ticket (thoughts?)

I think that would be helpful. What happens if a user imports a custom mira field file though? It would be confusing to still have the toggle if the functionality isn't there.

[BrandonPacewic]

Some small conflicts from #1251 but otherwise looks good.