AI Players static registration for debug menu and cleanup

[trevan]

This is for discussing two possible "static registrars". One for the debug menu and one for AI cleanup.

Debug Menu

Currently, there is code in DebugMenu that checks if any of the players are of type AbstractProAi. And if there is, it will then call AbstractProAi.initialize and add a menu option.

I'd like to add a DebugMenuRegistry that has a Map<String, Collection<Function<TripleAFrame, Collection<JMenuItem>>>. Callers would register their debug menu by specifying the name of the menu and the callback that will build the items in the menu. When DebugMenu is instantiated, it would have the map passed into it and it would construct the debug menu using that data.

AbstractProAi would then add code to its initialize to register its menu item.

Cleanup

Currently, the ProAI has a static gameOverClearCache method that is run at various points of game-core when the system is shutting down. I looked into moving the code into ProAi#stopGame but there are a few edge cases where stopGame isn't called but gameOverClearCache is (such as when an exception is thrown during a game or when the game is shutdown).

I'd like to allow my AI (and others) to hook into the same gameOverClearCache without needing to edit game-core. My thinking is to add a GameOverRegistry that has static methods for adding new callbacks (with a type similar to Runnable - no parameters, void return type). All the places that currently call ProAi#gameOverClearCache would be updated to instead grab the list of callbacks from GameOverRegistry and call them. The ai players would then be able to register their cleanup callbacks during initialize.

Thoughts?