Add ability to re-initialize AnchorStateRegistry with additional game types

[ajsutton]

Description

Adds an additional transaction template to #363 that re-initializes the AnchorStateRegistry to add an initial anchor state for new game types. The initial anchor state to use is taken from the current anchor state for another game type (at the time the just command is run so it's static in the resulting task definition).

This allows creating a task to enable permissionless fault proofs on a chain that previously only deployed permissioned games.

[mds1]

Similar to #363, just needs to be updated now that #356 was merged

[ajsutton]

@mds1 Just a heads up, I wound up changing this one a bit. Because the initialize method writes the supplied anchor states to it's storage but doesn't delete any other existing entries from the map, we can make the operation safer by only setting the new anchor states and not overwriting the existing source anchor state. I added a post-check to confirm the source anchor state is still set.

The base branch was changed.