Once stable, run Aztec Scenario Tests

[ludamad]

Aztec Scenario Tests

Full scenario test details: https://hackmd.io/@aztec-network/S19voVpAA

Intermediate steps: (ported from #9305)

• Get transfer test working against the cluster with 36s slot time, have metrics showing
• Get 4epochs test working against the cluster (coordinate with @ludamad)
• Start to build up to test scenario above, hit committee 16 with any TPS that runs for 4 epochs. Measure TPS
  • 36s per slot * 16 slots = 576s per epoch (9.6 min) (src)
• Work with team to find out what is needed to hit 0.1 TPS
• Add manual workflow that uses proving

Scenario Checklist

Stable Scenarios

The following tests can be completed today and are not blocked by pending features within the codebase.

• Test 1 - Testing the load bots
• Test 2 - Block building throughput of sequencer
• Test 3 - Test execution time
• Test 4 - Provernet Environment

Unstable Scenarios

These additional tests are currently on hold as they depend on features that are still under active development.

• Test 5 - S&P Testnet Environment - Pending Prover coordination feature(s)

• Epic: prover coordination #8679

• Test 6 - S&P Testnet Reorg Support - Pending reorg feature(s)

• feat: Handle reorgs on sequencer #9201
• bug: canPrune should take a time #9308

• Test 7 - S&P Testnet Upgrade Support - Pending governance upgrade feature(s)
• Test 8 - Bandwidth and hardware requirements - Valid, after all features are in place