fix: increase test timeout for heavy recursion tests in debug build (#22347)

## Summary
Fixes nightly barretenberg debug build failure (CI run
https://github.com/AztecProtocol/aztec-packages/actions/runs/24066248159).

**Root cause:**
`HonkRecursionConstraintTestWithoutPredicate/2.GenerateVKFromConstraints`
(root rollup circuit, the heaviest test variant) timed out at 601s
against the 600s default timeout. Exit code 124.

**Fix:**
- Bump timeout from 600s to 900s for `HonkRecursionConstraintTest` and
`ChonkRecursionConstraintTest` suites
- Add `ChonkRecursionConstraintTest` to the CPUS=4:MEM=8g resource group

Several other tests in these suites are also close to the 600s limit
(503s, 519s), so this prevents future timeouts as debug build overhead
grows.

**Note:** PR #22346 (from earlier session) is a no-op — the
logderivative fix it applies already exists on `next` via
merge-train/barretenberg (#22324). The actual failure was this timeout.

ClaudeBox log: https://claudebox.work/s/5f7d3bb56d7d756f?run=1

Author: AztecBot

barretenberg/cpp/bootstrap.sh

@@ -248,9 +248,13 @@ function test_cmds_native {
         local prefix=$hash
         # A little extra resource for these tests.
         # IPARecursiveTests fails with 2 threads.
-        if [[ "$test" =~ ^(AcirAvmRecursionConstraint|ChonkKernelCapacity|AvmRecursiveTests|IPARecursiveTests|HonkRecursionConstraintTest) ]]; then
+        if [[ "$test" =~ ^(AcirAvmRecursionConstraint|ChonkKernelCapacity|AvmRecursiveTests|IPARecursiveTests|HonkRecursionConstraintTest|ChonkRecursionConstraintTest) ]]; then
           prefix="$prefix:CPUS=4:MEM=8g"
         fi
+        # These tests routinely take 400-600s in debug builds; bump from the 600s default.
+        if [[ "$test" =~ ^(HonkRecursionConstraintTest|ChonkRecursionConstraintTest) ]]; then
+          prefix="$prefix:TIMEOUT=900s"
+        fi
         echo -e "$prefix barretenberg/cpp/scripts/run_test.sh $bin_name $test"
       done || (echo "Failed to list tests in $bin" && exit 1)
   done