Consider popping moves.Base, DefaultGameDelegate into separate package

[jkomoros]

Named defaults. Would allow a global IsFixUp() method to cast the move to see if it has FixUp and then return the value as a convenience (so that boardgame.Move can lose that method, which is weird to be in the base package given it doesn't actually do anything)

Originally captured in #633.

[jkomoros]

Also, should they be named the same thing?

[jkomoros]

Also could move boardgame.BaseSubState, probably others

[jkomoros]

• [x] DefaultGameDelegate.SanitizationPolicy loses the dependency on the private validator. (Does this imply moving the auto-inflation behavior into a sub-package (perhaps an internal package?)
• [x] Move BaseSubState to base.SubState
• [x] Move BaseComponentValues to base.ComponentValues
• [x] Create base/ package and move DefaultGameDelegate to base.GameDelegate
• [x] Move moves.Base to base.Move. (will need some way of factoring out the reliance on custom configuration, or have for example a ExtractName(customConfiguration) string for every With() type, or a ValuExtractor(PropertyCollection) that has the typed getters for each thing in the library, so it only has one documentation entry point.) (grep for all uses of moves.Base in documentation) (moves.Base is pretty entertwined with a lot of logic in the moves package. Maybe have base.Move which only does extremely basic things, and then moves.Default which is the current moves.Base?)
• [ ] get rid of defaultGameDelegate in main library (just move those implementations onto the test game delegate)
• [x] base.IsFixUp(move boardgame.Move) that extracts the IsFixUp of the move and returns it, or false if no IsFixUp method. (and remove IsFixUp from core library)
• [x] Scrub all documentation to talk about the base package and ensure everything that used BaseSubState, BaseComponentValues, DefaultGameDelegate, moves.Base etc all use the proper name
• [x] Should delegate.CurrentPhase and PhaseEnum be popped out into base.GameDelegate? (issue #654)
• [x] Update TUTORIAL.md and ensure all documentation matches
• [ ] Update games in games repo

[jkomoros]

A lot of the tests in the main package rely on defaultgamedleegate. Could just duplicate the code into the main package for testing, or could pop out the game logic into an internal testgame package. (The main package can't trigger it because it'd need to import it and that would create a cycle.) This would also resolve an issue of the generic test game (what issue number is that?)