Game Piece Asset Support [AARD-1902]

[azaleacolburn]

Description

Game pieces are now treated as separate assets from the field, they are able to be spawned, deleted, cached, etc, all on their own.

Objectives

• Frontend configuration menu for game pieces
• Game pieces are returned as separate assemblies
• Game pieces are pruned from the main assembly
• Game pieces are treated like separate entities, neither fields nor robots and are configurable
• Game pieces still start in the same place on the field as before
• Game pieces cache properly
• Game pieces can be interacted with by robots as before
• Game pieces work in match mode as before

Testing Done

• Parsing fields (2023 & 2024) still works
• Game pieces can still be manipulated
• Game pieces can be configured
• Configuration and spawning UI works

Note

Fields no longer spawn with a transform gizmo attached

AARD-1902

[BrandonPacewic]

Tests are currently failing, looks like it might be similar to #1222 but want to confirm.

[Dhruv-0-Arora]

@BrandonPacewic @azaleacolburn this PR just requires merge conflicts resolution, correct?

[BrandonPacewic]

After looking into the tests I think this is a separate issue and one that is introduced by this PR. Please take a look.

[azaleacolburn]

This was also a refactor

[BrandonPacewic]

When I click on Configure Assets and go to the Pieces tab all I see is the current field. If I select it I don't see any other options:

When spawning fields the game pieces don't appear to be aligned properly. I remember this coming up in discussions at one point but I don't remember what the conclusion of it was.

[azaleacolburn]

When spawning fields the game pieces don't appear to be aligned properly. I remember this coming up in discussions at one point but I don't remember what the conclusion of it was.

This issue is caused by the transform on the part instance being miscalculated in the exporter. This wasn't an issue before since we used the field rigid node rather than the independent part transform. The pieces aren't off by a consistent amount across fields, so here's what I'm going to do:

1. See if I can get a transform from the field rigid node to use for alignment
2. Since all the pieces are off by the same amount within each field, I could have a map of transform adjustments to fix this for out (incorrectly exported) fields.