chore(test): Run test matrix on test_programs

[aakoshh]

Description

Problem*

Resolves #6390

Summary*

Runs the test_programs with -Inf, 0 and +Inf --inliner-aggressiveness before we can change the default from +Inf (inline everything) to 0.

There are some test failures triggered by this, which need to be fixed before merging this:

• Test brillig_cow fails with inliner = -Inf #6439
• Test closures_mut_ref fails with inliner <= 0 and brillig #6440
• Test eddsa fails with inliner = -Inf #6441
• Test missing_closure_env fails with inliner <=0 and brillig #6442
• Test references fails with inliner = -Inf and brillig #6443
• Test slice_dynamic_index fails with inliner = -Inf and brillig #6444

Additional Context

A specific test can be executed like so:

cargo test -q -p nargo_cli --test execute <test-name>

Consistent test failures are (created tickets for them, see above):

    tests::execution_success::test_brillig_cow::false_i64_min_expects
    tests::execution_success::test_brillig_cow::true_i64_min_expects
    tests::execution_success::test_closures_mut_ref::true_0_expects
    tests::execution_success::test_closures_mut_ref::true_i64_min_expects
    tests::execution_success::test_eddsa::true_0_expects
    tests::execution_success::test_eddsa::true_i64_min_expects
    tests::execution_success::test_missing_closure_env::true_0_expects
    tests::execution_success::test_missing_closure_env::true_i64_min_expects
    tests::execution_success::test_references::true_i64_min_expects
    tests::execution_success::test_slice_dynamic_index::true_i64_min_expects

Note that instead of the _brillig suffix we have ::true_ indicate which tests are run with --force-brillig.

All failures are under execution_success, so I switched off the inlining matrix for the other test types; doing so impoves the runtime by 15-30%.

Another bug independent from inliner aggressiveness was #6445 This existed in the codebase before and I have seen it locally, but it never seemed to have affected CI; it probably uses less threads. I fixed it in this PR; since it affected test code generation I didn't think a separate PR would be helpful.

Documentation*

Check one:

• No documentation needed.
• Documentation included in this PR.
• [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

• I have tested the changes locally.
• I have formatted the changes with Prettier and/or cargo fmt on default settings.