Tracking issue for testing every feature of v5

Tracking issue for testing every feature of v5:

• Can launch RL and bots on Windows
• Can launch RL and bots on Linux
• Can launch RL via Heroic and Legendary
• Matches can be started via paths to toml files
• Matches can be started via MatchConfigurations
• Every field of the match configuration has the expected effect and appropriate default value
  • Bot names can be overridden
    • Overriding a Psyonix bot's name to a Psyonix preset results in the corresponding loadout too (unless loadout is overridden)
  • Bot loadouts can be overriden
  • Every mutator works, in particular those that affect GamePacket values
    • Multiple balls work
    • Boost recharge works
    • Extended dodge timer works
    • Multiple jumps work
    • ...
• Hiveminds consist of bots with the same agent id and team, only
• Scripts work
• Bots can set loadout during initialization, even when state setting is off
• Bots can set loadout mid-match when state setting is on
• Every field of the game packet is reported correctly, in particular
  • Jump/dogde timers and flags, even when Mutators are applied
  • Humans are always at the end of the game packet player list
  • Last spectated player
  • Player last input
  • Player accolades
  • ...
• Ball prediction works, in all arenas and with relevant mutators
• Matches can be started in Freeplay
• All debug rendering renders as expected
• Debug rendering can be toggled for individual bots/scripts, unless the rendering setting is AlwaysOff
• Game state setting works as expected
• Match comms work as expected
  • Only received by expected clients and contain correct meta data
  • Match comms are displayed faithfully to quick chat (also in overtime?)
• Match runners can observe game packets and
  • Use match commns
  • Use debug rendering
  • Use state setting

Ideally, we add unit/system tests where possible.

Feel free to propose more entries for the list.

Start with the unchecked entries in this tracking checklist, prioritizing one specific feature or behavior rather than the whole issue. Add unit or system tests where possible, then verify the corresponding checklist item against the expected behavior; the issue is done only when the remaining applicable entries have been tested.