ABANDON THREAD

I like part of where this code is going but I've also made too many
little mistakes.  Committing what I've done and spawning off a new
branch to try a different approach.
delete game file
create the game module
Create the test files for the new game subpackage
preliminary breaking tests setup
Added a windows batch file to run tests on file changes
gamestate is missing
player is missing

I'm stretching this out, but the idea is to write unit-tests, run them,
and on error fix the error.
Create dungeon module, Dungeon class, import to gamestate
Test isolation fix

Player class should not know ANYTHING about gamestate, it should be a
one way street where gamestate tells player what to do and player
may/may not know anything else
cleanup and start fixing test failures
Fix test_reload_player, add Create_Rebuild
fix spelling error ( casing )
add expected params to fix failing test
Now with tests in place...

I'm starting to see/realize the funky bits off how I was thinking Player
class should work, and cleaning them up.
Lots of work, but all tests passing now!

This doesn't mean it's done or it works, just that the tests that are
here pass.
Watch for json also
Update our requirements!
Add coverage plugin (temporarily)
Cleanup, convert connections values to Room object refs, implement get method