fix(ci): raise AVM check-circuit input timeout

[AztecBot]

Summary

• Raise the dumped AVM check-circuit per-input timeout from 30s to a 120s default.
• Make the timeout overridable with AVM_CHECK_CIRCUIT_TIMEOUT.
• Update the harness comment to account for larger valid block-building inputs such as multiple_blobs.

Root cause

The failed avm-check-circuit job in https://github.com/AztecProtocol/aztec-packages/actions/runs/29954846224 did not hit a circuit mismatch. The child dashboard log 7c7d1e792056f927 shows the single-node/block-building/multiple_blobs dumped input reached Running check (with skippable) circuit over 700560 rows, then GNU timeout killed it at the hard-coded TIMEOUT=30s. The parent job reported exit code 124.

Testing

• bash -O extglob -n yarn-project/end-to-end/bootstrap.sh
• git diff --check
• Smoke-generated an avm_check_circuit_cmds command for a representative multiple_blobs input and confirmed it emits TIMEOUT=120s.

---

Created by claudebox · group: slackbot

[AztecBot]

Superseded by #24959, which makes the same avm_check_circuit budget fix, is rebased on current next (so its CI is meaningful), and carries the evidence from the latest failure (run 30266937162).

Five open PRs plus ~50 stale branches all propose this same one-line change and none has ever landed. Consolidating on #24959 — safe to close this one.

---

Created by claudebox · group: slackbot

[AztecBot]

Closing in favour of #24959, which carries the same fix rebased onto current next plus the consolidated evidence (including the circuit check: success / check_circuit_ms: 19601 sub-log from #24950 and the 22.75s local measurement from #24946).

This is a consolidation, not a rejection — the analysis here was correct. Six identical open drafts were competing for the same review, and each was expiring to the stale-draft closer before anyone looked. Please review and merge #24959 to break the loop.

---

Created by claudebox · group: slackbot