[Dev]: Cold Storage Data Structures

[TylerBloom]

Unmet Need:

Tournaments track lots of redundant data that is useful during the tournament, but that data takes up too much space after it is over. Excess data that can be trimmed includes the confirmations and drops in a round, round number to id map and opponents being tracked in the round registry, name to id map in the player reg, deck ordering in the player, and most importantly, everything back a unique identifier for all cards in decks.

Challenges/Considerations:

As stated, only tournament data needs to be in long-term storage, not tournament managers. However, we want to periodically save whole tournaments and their operation logs for regression testing.