fix(ci): raise AVM check-circuit timeout

[AztecBot]

Summary

• Raise the dumped AVM check-circuit per-input timeout from 30s to 90s.
• Add AVM_CHECK_CIRCUIT_TIMEOUT so CI can tune the timeout without editing the command generator again.

Root cause

The scheduled AVM check-circuit run on next failed because one large dumped input timed out, not because the circuit check reported unsatisfied constraints. The failed command was:

bb-avm avm_check_circuit -v --avm-inputs yarn-project/end-to-end/dumped-avm-circuit-inputs/e2e_multiple_blobs/avm-circuit-inputs-tx-0x2d946dfdd36a2467dc22f415c24db6946b14946b134649c449dcccc83c9c38a1.bin

The CI dashboard log shows it reached Running check (with skippable) circuit over 700560 rows and was then terminated by timeout -v 30s with exit code 124. The existing script comment already warned that larger transactions could outgrow the hard-coded timeout; this input did.

Validation

• ./bootstrap.sh avm_check_circuit_cmds from yarn-project/end-to-end with a synthetic dumped input emits TIMEOUT=90s.
• AVM_CHECK_CIRCUIT_TIMEOUT=120s ./bootstrap.sh avm_check_circuit_cmds emits TIMEOUT=120s.
• bash -O extglob -n yarn-project/end-to-end/bootstrap.sh
• git diff --check

Note: a plain bash -n does not parse this pre-existing script because it contains extglob patterns; bash -O extglob -n is the relevant syntax check.

---

Created by claudebox · group: slackbot

[AztecBot]

Flakey Tests

🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry.

\033FLAKED\033 (8;;http://ci.aztec-labs.com/8544fb49e384ebca�8544fb49e384ebca8;;�):  yarn-project/end-to-end/scripts/run_test.sh simple src/e2e_epochs/epochs_high_tps_block_building.test.ts (295s) (code: 0) group:e2e-p2p-epoch-flakes

[AztecBot]

Automatically closing this stale claudebox draft PR (no updates for 5+ days). Re-open if still needed.