Make sure all example games follow all best practices

[jkomoros]

E.g use DefaultMove, all naming schemes, what's public and private

[jkomoros]

• Have the right things public and private
• Use idiomatic naming schemes for moves, move factories, etc
• Have moves broken up into the proper granularity
• Signal to trigger other moves in a canonical way
• Use PlayerIndex.Next(), Valid(), etc appropriately
• Check for all illegal moves
• Use autoreader
• Name of decks is set reasonably so the dom-module will have a reasonable name
• Defining methods on state structs that are then reflected as computed values
• Move Factories return the concrete type, not boardgame.Move
• Illegal moves about turn use proper voice (see #345)
• Proper use of timers and animation delays
• Move's Description() returns a good string in proper voice
• Use moves.Base, moves.CurrentPlayer where appropriate
• Use Enums in appropriate places, initialized in an idiomatic way, and using autoreader generation
• NewManager returns (manager, error), MustNewManager panics (but that means that internal to NewManager there shouldn't be an Must things that will panic)
• Use auto-inflation for all state objects
• Various Constructor methods should not do any defaults-setting, only zero-value setting
• Have at the very least a test that creates a new manager and checks for nil err
• Moves all call their super's Legal method
• Game set up (e.g. initial deals) should happen as setup moves with move progressions, not in FinishSetUp (unless you only have one round and don't care about setup being animated). Basically, it should be trivial to have a game have multiple rounds
• BulkAddMoveTypes and AddMovesForPhaseProgression in NewManager should have their errors inspected
• Moves should be named MoveThingThatWillHappen, and if the struct doesn't ahve non-trivial methods then it shouldn't exist and instead just use AutoConfig with the right config methods.
• Moves should be in separate files for each phase moves_playing.go, moves_setup.go
• only NewDelegate should be exported from the package

[jkomoros]

Related: heavily comment the examples so that they can be used like a tutorial

[jkomoros]

MoveConstructor's constructor should have BaseMove be a named argument so that the other values can be omitted, e.g.

    MoveConstructor: func(mType *boardgame.MoveType) boardgame.Move {
        return &MoveActivateHandmaid{
            BaseMove: boardgame.BaseMove{mType},
        }
    },