op-node/rollup/derive: Implement pipeline stage multiplexing

[sebastianst]

Description

This PR implements derivation pipeline stage multiplexing to achieve stage transformations of the channel and batch stage for Holocene.

Stage Multiplexing

The channel and batch stage of the derivation pipeline have two separate implementations for those stages pre- and post-Holocene, and a transformation should happen between those stages when the L1 origin goes past the Holocene activation timestamp (and back if a reset occurs).

• BatchQueue -> BatchStage
• ChannelBank -> ChannelAssembler

This PR adds the concept of stage transformations to the derivation pipeline. A stage can be a

type ForkTransformer interface {
	Transform(rollup.ForkName)
}

to implement stage-specific transformation behavior for a particular fork. When the derivation pipeline's Step function detect an L1 origin timestamp going past a Fork activation point, it iterates over all stages and calls the transformation function. This is currently optional per stage, so Go interface conversion tests are used to check whether a stage has transformation functionality implemented.

This design allows for a modular stage transformation design that encapsulates fork-specific logic to each individual stage.

In this PR, the new architecture is used in two different ways:

• The FrameQueue implementation type and instance stay the same pre- and post-Holocene. However, Holocene consensus rules require the frame queue to be reset at Holocene activation. So the FrameQueue was made a ForkTransformer for Holocene, and simply resets itself.
• The channel and batch stages have two different implementations pre- and post-Holocene. So-called stage multiplexers ChannelMux and BatchMux were added which orchestrate the transformation of the pre-Holocene stages into the post-Holocene stages.
  • They call the underlying transformHolocene() functions on the legacy ChannelBank and BatchQueue stages to obtain the Holocene stages. In the case of the BatchQueue this allows to port over the collected l1Blocks into the new Holocene BatchStage.
  • When Reset would go back to an L1 origin pre-Holocene, the multiplexers also transform back to the reset pre-Holocene stages.

Fork modularity

In anticipation of improved modularity of the codebase around forks, this PR prepares some generic fork functionality for the deploy config and in action test. Also, a common action test environment was added. In future work, existing action tests will be simplified to use the new environment.

Tests

Added action tests that check for the correct stage transformation log messages. The two cases tested are

• Holocene at Genesis: immediate transformation
• Holocene post-Genesis: transformation at the Holocene L1 origin and reset back to a pre-Holocene derivation state.

Metadata

• Fixes Holocene-D: Activation pipeline reset and stages wiring #12157

[semgrep-app]

Semgrep found 1 sol-style-notice-over-dev-natspec finding:

• packages/contracts-bedrock/src/cannon/interfaces/IPreimageOracle.sol
  • L25 - Triage

Prefer @notice over @dev in natspec comments

_{Ignore this finding from sol-style-notice-over-dev-natspec.}

Semgrep found 1 golang_fmt_errorf_no_params finding:

• op-deployer/pkg/deployer/bootstrap/bootstrap.go
  • L63 - Triage

No fmt.Errorf invocations without fmt arguments allowed

_{Ignore this finding from golang_fmt_errorf_no_params.}

[sebastianst]

A few remarks for reviewers.

[ajsutton]

Looks good, but seem to have some test failures.

[ajsutton]

Approving as I don't think there's anything really blocking in my comments. Obviously the tests will have to pass though. :)