feat: support legacy zkevm-node and new zkevm sequence senders and aggregators

[leovct]

Description

In #193, we introduced cdk-node as the default sequence sender / aggregator component for the CDK stack. In this effort, we removed support for the legacy zkevm-node sequence sender and aggregator as well as the new zkevm components, zkevm-sequence-sender and zkevm-aggregator. However, this is something we still need to test.

This PR introduces a new flag sequence_sender_aggregator_type to specify the type of sequence sender and aggregator to deploy. There are 3 options:

• cdk: Use the new cdk-node.
• new-zkevm: Use the new zkevm components: zkevm-sequence-sender and zkevm-aggregator.
• legacy-zkevm: Use the legacy zkevm-node sequence sender and aggregator.

The following diagram describes what kurtosis-cdk currently deploys (only for the central environment).

And the following diagram represents what kurtosis-cdk will be able to deploy with this new change.

The deploy workflow has been updated to test different scenarios listed under .github/tests. For example, the scenario erigon-sequencer-cdk-stack-cdk-validium-da.yml will deploy a devnet with an L1 and a CDK L2 with erigon as the sequencer, the cdk-node as the sequence sender / aggregator and the chain will be a CDK validium.

$ ls -l .github/tests
total 48
-rw-r--r--  1 leovct  staff  126 Aug 27 09:49 additional-services.yml
-rw-r--r--  1 leovct  staff  172 Aug 27 10:28 erigon-sequencer-cdk-stack-cdk-validium-da.yml
-rw-r--r--  1 leovct  staff  178 Aug 27 10:31 erigon-sequencer-new-zkevm-stack-cdk-validium-da.yml
-rw-r--r--  1 leovct  staff   43 Aug 27 10:33 gas-token.yml
-rw-r--r--  1 leovct  staff  180 Aug 27 10:29 legacy-zkevm-stack-cdk-validium-da.yml
-rw-r--r--  1 leovct  staff  174 Aug 27 10:29 legacy-zkevm-stack-rollup-da.yml

References (if applicable)

https://0xpolygon.slack.com/archives/C06M06XR5A4/p1724233695796189

[jhkimqd]

Tested locally and lgtm.
Might be worth noting somewhere that the legacy configs may not work with CDK-Erigon configs. e.g. aggregator_sequence_sender_type and sequencer_type had to be both zkevm to work on my test.

[leovct]

Tested locally and lgtm. Might be worth noting somewhere that the legacy configs may not work with CDK-Erigon configs. e.g. aggregator_sequence_sender_type and sequencer_type had to be both zkevm to work on my test.

I think we should aim to cover scenarios 1, 2, 4, 7 and 8. I updated the CI jobs to test that.

[leovct]

This PR also cleans up some parts of the CDK central environment (e.g. how sequencer is deployed, how aggregator / sequence sender is deployed, etc.). The central RPC deployed will be of the same type as the sequencer. For example, if sequencer_type is equal to erigon, it will automatically deploy a cdk-erigon-node rpc. Same thing if sequencer_type is equal to zkevm, it will deploy a zkevm-node rpc.

[leovct]

Update before I leave for a few days: every scenario work except the one with cdk-erigon as the sequence and the new zkevm components (zkevm-sequence-sender and zkevm-aggregator). Batches are being virtualized but not verified. I tried to bump the images but it looks like there is still an issue with the aggregator.

https://github.com/0xPolygon/kurtosis-cdk/actions/runs/10601202150/job/29380486728?pr=234#step:6:1654