Added initializeAnchorStateRegistry config. Update Fault Proof config

[jcortejoso]

Added a new config flag initializeAnchorStateRegistry to skip the initialization of AnchorStateRegistry in the execution of Deploy.s.sol. This, can be initialized latter when the faultGameGenesisOutputRoot is known.

Also updated the config template in config-vars-celo.sh to match OP Mainnet and Sepolia FaultProof config.

[piersy]

Hey @jcortejoso, what I'm not understanding here is how was this working for optimism? Because you need to have done the l1 deployments in order to generate the l2 genesis allocs, and here in order to call initializeAnchorStateRegistry you need to have the l2 genesis. So it seems like it could never have worked for them?

[jcortejoso]

@piersy my understanding is that OP deployment has been different from us, and they introduced Fault Proofs in a posterior upgrade, so they can init the state to an arbitrary existing block:

This is initialized with the starting anchor for CANNON and PERMISSIONED_CANNON games set to block number 120059863 and output root 0x2694ac14dcf54b7a77363e3f60e6462dc78da0d43d1e2f058dbb6a1488814977.

I wonder for a migrated network in our case we could use a pre-migration block as anchor for the deployment. My concern if that can be risky because op-proposer may require archive data afaik.