[CODE] Declassify Game

[j-gynn]

Description
Game (the class) and game (the object we call) don't need to exist the way they do. The Pythonic way of doing a singleton is through the Global Object Pattern. Related justification for why Singletons aren't used in Python.

The game-related functions can be placed into a file called game.py, which could be imported such that all previous calls to game.clan, game.switches etc. are all still functional without changes.

This would also (hopefully) mean that our tests can actually access things in game, or at least that we can write a pipeline function to build game and make it available to them. This should remove the confusing overhead we have of code intentionally taking a different route when running in tests (which is explicitly the opposite of what tests should do!).

This is tangentially related to #2515.

Requirements:

MUST

• Remove class Game and game = Game()
• Must NOT change calls to game elsewhere in code; i.e., ensure functionality is accessed in the exact same way as before
  • Where this is not possible, changes MUST be documented and clearly rationalised

[rustykitty]

/assign-me

[github-actions]

👋 Hey @rustykitty, thanks for your interest in this issue! 🎉

⚠ Note that this issue will become unassigned if it isn't closed within 7 days.

🔧 A maintainer can also add the 📌 Pinned label to prevent it from being unassigned automatically.