Major asteroids refactor

[NicolenaStiles]

Take knowledge gleaned from breakout implementation and add in (at minimum):

• [ ] game state management
• [ ] pop up dialog boxes to explain user navigation
• [ ] hyperdrive
• [ ] compatibility with other widgets (flutter wrapper)

[NicolenaStiles]

Also:

• [x] mess with input controls and see if I did those correctly

[NicolenaStiles]

Spent the entire day trying to figure out how this will play with my actual website. Following options are the ones that make the most sense for desired behavior:

1. Use the overlays from Flame itself, even though I have no idea how that will interact with my Go Router
2. Run the game in an isolate that still animates in the background
3. Find some way to more cleverly pass state between all those GameWidget calls?
4. Bypass this discussion entirely and generate some gifs of the asteroids moving or something idk

[NicolenaStiles]

Current effort: add in play_area.dart logic from this codelab to better handle object collisions offscreen. Very possible this is a bad idea but I am eager to find out.

[NicolenaStiles]

Getting some major issues with framerate speeds using the current moveEffect calls.

This commit has me saving state before trying to remove those calls and get the framerate back up.