feat: custom rollup config

[zobront]

Add support for a rollups outside of the superchain-registry via a dynamic RollupConfig.

Overview

Program Changes

• The fault-proof and range programs now take in a BootInfoWithBytes config that contains the rollup_config_bytes. These bytes are hashed inside of the program to get the rollupConfigHash which is committed to within the rollupConfigStruct. The RollupConfig is used in the BlockExecutor.
• The aggregation program verifies that the rollupConfigHash committed to in each range proof is the same, and the rollupConfigHash is then verified to match the one stored in the contract on-chain. This guarantees that only 1 rollupConfigHash can be used at a time.

Script Changes

• Whenever the fetcher is initialized, save the rollup config for the corresponding chain to rollup-configs/{chain_id}.json. This path is used during witness generation, so it's important that the relevant rollup configuration is present at that path.
• Modify the BootInfoStruct to include the rollup_config_hash.

Contract Changes

• Add a check for the rollupConfigHash whenever proposeL2Output root is called on ZKL2OutputOracle.
• Before reading the zkl2ooconfig.json, build & invoke the fetch-rollup-config binary, which updates the vkey, startingBlockNumber, chainId, l2BlockTime, rollupConfigHash, startingOutputRoot and startingTimestamp. To use a manually set startingBlockNumber, set USE_CACHED_STARTING_BLOCK in your environment.

Miscellaneous

• Add support for using the cached starting block in the zkl2ooconfig.json, rather than re-initializing it.
• Fix an issue in the cost estimator that didn't handle span batches with the same start and end block.
• Remove unnecessary TODO's and unused documentation from the book.
• Exit the native_host_runner correctly.
• Remove the annotation for the ec_recover precompile as it's infrequently used.
• Move .env.example to the root.

TODO's

Remaining:

• Do an E2E test of span and agg proofs with new code. Note that this will require deploying a new contract (with the rollup config hash added) to verify proofs against.
• Update tutorial in other PR to include calling cargo run --bin fetch_rollup_config before deploying contracts.