fix(ci): extend AVM check-circuit timeout for multiple blobs

[AztecBot]

Root cause:

• The AVM check-circuit run failed in the per-input timeout, not from a circuit constraint failure.
• In run https://github.com/AztecProtocol/aztec-packages/actions/runs/27572690221, e2e_multiple_blobs/avm-circuit-inputs-tx-0x28d7d0ab...bin reached Running check (with skippable) circuit over 700560 rows. and was killed by timeout -v 30s with exit code 124.
• A prior same-day failure hit the same e2e_multiple_blobs path with the same row count, so this is the fixed 30s budget being too low for the heavier multiple-blobs circuit inputs.

Fix:

• Keep the existing 30s budget for ordinary dumped AVM inputs.
• Emit TIMEOUT=120s for e2e_multiple_blobs* dumped inputs, which are known to produce much larger circuits.

Evidence:

• Current GitHub run: https://github.com/AztecProtocol/aztec-packages/actions/runs/27572690221
• Current parent CI log: http://ci.aztec-labs.com/1781554977613885
• Current failing child log: http://ci.aztec-labs.com/89fb233961741538
• Prior GitHub run: https://github.com/AztecProtocol/aztec-packages/actions/runs/27554964039

Validation:

• git diff --check origin/next...HEAD
• bash -O extglob -n yarn-project/end-to-end/bootstrap.sh
• Ran ./bootstrap.sh avm_check_circuit_cmds with temporary fake dumped inputs and verified normal inputs still emit TIMEOUT=30s while e2e_multiple_blobs emits TIMEOUT=120s.

Not run:

• Full local avm_check_circuit; this checkout does not have a built bb-avm binary or the dumped CI input artifact locally.