feat(conductor)!: implement v2 execution API

[ethanoroshiba]

Summary

Updates Conductor to use v2 Execution API, including use of new "execution sessions".

Background

These changes are necessary to support migrating Forma to mainnet.

Migrating Forma to Astria's main net requires introducing stop and start logic into the Conductor. A migration using these changes could look like this:

1. Running against a fresh rollup node, Conductor starts and initiates a new execution session via astria.execution.v2.CreateExecutionSession, which contains rollup_start_block_number = 1, and rollup_end_block_number = 1000.
2. Conductor executes (syncs) the rollup node from rollup block numbers 1 to 1000 (inclusive)
3. Upon executing rollup number 1000, conductor resets its inner state and initiates a new execution session via astria.execution.v2.CreateExecutionSession, with new information from which it will continue executing.

For cases where rollup_end_block_number is unset (or equivalently set to 0), conductor will never restart as there is no stop condition.

For conductors running in firm-only or in soft-and-firm modes, only the firm-executed block triggers a restart (in soft-and-firm mode, upon soft-executing at the rollup stop number no blocks will be executed past it).

For conductors running in soft-only mode the soft-executed block triggers the restart.

If the rollup chain is halted, it should respond with tonic::Code::FailedPrecondition to CreateExecutionSession, which will cause the Conductor to shut down upon attempting a restart.

The aforementioned rollup changes to be made in astria-geth necessitate changing our current charts config for the following. "Forks" now describes a set of instructions for when and how to stop and restart the EVM at different heights, such that changes (such as network migration) can be made.

config:
        # < non astria-prefixed items... >
        AstriaOverrideGenesisExtraData:
        AstriaRollupName:
        AstriaForks: []
                # - < fork name >:
                #         height: ""
                #         halt: ""
                #         snapshotChecksum: ""
                #         extraDataOverride: ""
                #         feeCollector: ""
                #         EIP1559Params: {}
                #         sequencer:
                #                 chainId: ""
                #                 addressPrefix: ""
                #                 startHeight: ""
                #         celestia:
                #                 chainId: ""
                #                 startHeight: ""
                #                 searchHeightMaxLookAhead: ""
                #         bridgeAddresses: []

Changes

In astria-core

• Replaced v1 execution domain types with v2 execution domain types:
  • ExecutionSession
  • ExecutionSessionParameters
  • ExecutedBlockMetadata
  • CommitmentState (name unchanged, but fields are)
• For more information on API changes, see feat(proto): create v2 execution API #1962

In astria-auctioneer

• Updated execution types to v2

In astria-conductor

• Changed sequencer-to-rollup-height calculation to start from rollup_start_block_number in ExecutionSessionParameters, so that Conductor doesn't start from rollup height 1 again after restarting.
• Removed ASTRIA_CONDUCTOR_SEQUENCER_CHAIN_ID and ASTRIA_CONDUCTOR_CELESTIA_CHAIN_ID env vars from Conductor (chain ID checks will now be performed against the values retrieved from the genesis info)
• Added restart logic for when the stop block number is reached: Conductor will restart at the stop height and initiate a new execution session
• Removed multiplication of Celestia variance.

In charts

• Added astriaForks to EVM rollup config, to reflect changes in astria-geth: https://github.com/astriaorg/astria-geth/pull/59/files.
• Add just command for deploying the EVM rollup restart test, which functions the same as our regular smoke test with a restart at sequencer height 20.

Testing

• Added miscellaneous unit tests to ensure heights are correctly calculated and whether to restart is successfully determined.
• Added blackbox tests to ensure conductor correctly restarts in each mode, and continues to execute at the correct height after initiating a new execution session.
• Added EVM rollup restart test which restarts EVM and Conductor at sequencer height 20 during the regular smoke test.

Changelogs

Changelogs updated

Breaking Changelist

• Domain v1 execution types have been almost entirely replaced
• Breaks Conductor config
• v2 Execution API changes are breaking from v1. v1 Conductor will only work with the v1 API, same for v2.

Related Issues

closes #1994
closes #2003