feat(test): Run test matrix on stdlib tests

[aakoshh]

Description

Problem*

Resolves #6349

Summary*

Added a test_matrix around run_stdlib_tests to call it with/without forcing Brillig and to try various inlining aggressiveness (min, 0, max).

Additional Context

The syntax to call a specific test still works, but now it runs with all compiler options combinations from the matrix:

❯ cargo test -q -p nargo_cli --test stdlib-tests -- run_stdlib_tests trait_eq::inequality

running 6 tests
[stdlib] Testing collections::bounded_vec::bounded_vec_tests::trait_eq::inequality... ok
[stdlib] 1 test passed
[stdlib] Testing collections::bounded_vec::bounded_vec_tests::trait_eq::inequality... ok
[stdlib] 1 test passed
[stdlib] Testing collections::bounded_vec::bounded_vec_tests::trait_eq::inequality... FAIL
Failed to solve program: 'Failed to solve brillig function'

error: Failed to solve program: 'Failed to solve brillig function'
    ┌─ std/collections/bounded_vec.nr:598:20
    │
598 │             assert(bounded_vec1 != bounded_vec2);
    │                    ----------------------------
    │
    = Call stack:
      1. std/collections/bounded_vec.nr:598:20

[stdlib] 1 test failed
[stdlib] Testing collections::bounded_vec::bounded_vec_tests::trait_eq::inequality... ok
[stdlib] 1 test passed
[stdlib] Testing collections::bounded_vec::bounded_vec_tests::trait_eq::inequality... ok
[stdlib] 1 test passed
[stdlib] Testing collections::bounded_vec::bounded_vec_tests::trait_eq::inequality... ok
[stdlib] 1 test passed
..F...
failures:

---- run_stdlib_tests::true_0_expects stdout ----
thread 'run_stdlib_tests::true_0_expects' panicked at tooling/nargo_cli/tests/stdlib-tests.rs:100:5:
assertion failed: test_report.iter().all(|(_, status)| !status.failed())
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    run_stdlib_tests::true_0_expects

test result: FAILED. 5 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.13s

error: test failed, to rerun pass `-p nargo_cli --test stdlib-tests`

This error was fixed by #6355

We can also run just the one combination that failed like so:

cargo test -q -p nargo_cli --test stdlib-tests -- run_stdlib_tests::true_0 trait_eq::inequality

Running all tests uncovered more problems:

❯ cargo test -q -p nargo_cli --test stdlib-tests 

..
[stdlib] Testing hash::assert_pedersen... error: Argument is not constant
   ┌─ std/hash/mod.nr:82:5
   │
82 │     crate::assert_constant(domain_separator_bytes);
   │     ----------------------------------------------
   │
   = Call stack:
     1. std/hash/mod.nr:82:5

...
[stdlib] Testing schnorr::test_zero_signature... error: Argument is not constant
   ┌─ std/hash/mod.nr:82:5
   │
82 │     crate::assert_constant(domain_separator_bytes);
   │     ----------------------------------------------
   │
   = Call stack:
     1. std/hash/mod.nr:82:5

[stdlib] 76 tests passed, 2 tests failed
...
failures:
    run_stdlib_tests::true_0_expects
    run_stdlib_tests::true_i64_min_expects

test result: FAILED. 4 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 1.31s

error: test failed, to rerun pass `-p nargo_cli --test stdlib-tests`

This was fixed by #6350

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.