Morph Delegate to GameManager concept

[jkomoros]

To underline that it's not actually a game that should be modified, just have e.g. its chest used as an example.

Important after we fix #81 and #94

[jkomoros]

Actually JK, Delegate should be renamed GameManager. It should have all of the current delegate's methods, as well as Chest(), Storage(), NewGame(), and lose the Game bit

[jkomoros]

Should game manager be the thing that applies moves to the canonical games?

[jkomoros]

• [x] Moves list should be on manager. Game maintains those methods, but only to DefaultForState them. Make sure to run go test ./... !!
• [x] Chest should move to Manager (game.Chest() can still just alias to that)
• [x] Storage should be on Manager, not game
• [x] Delegate should lose the SetGame method and Game reference (so they can be used for multiple games). (Update comments on GameManager)
• [x] Game.Name should actually be on GameManager
• [ ] NewGame() on Manager

[jkomoros]

Should NewGame be on manager? Currently newGame just creates a game object with things init'd. But the NewGame() package methods return a new, set up game. Most of the overhead is in new manager.

... Yeah, I think that for testing the boardgame package I still want newGame so I can call setUp later. But in general usage manager.NewGame() returning a SetUp'd game is more useful and less error prone.

[jkomoros]

Nah, it's not useful to have manager.NewGame, because SetUp() returns its own error, and it's weird and clunky to wire that back, too.

So now everything's done on this ticket.