feat: nargo test -q (or nargo test --format terse)

[asterite]

Description

Made on top of #6728

Problem

Towards #6733

Summary

Eventually we'll have nargo test --format json, which is what #6733. As a first step I wanted to introduce the format flag and, to try that abstraction in code I introduced a terse formatter similar to Rust.

On failure we don't immediately print the error. Instead, it's printed at the end (like in Rust). I can imagine this could be used in CI to reduce the output verboseness, because I guess all that matters in CI is seeing which tests failed. NOTE: I already added this -q flag to our external checks, you can see how it looks, I think it's a bit better as it's less noisy.

Like in Rust, there are two ways to trigger this terse behavior: -q (or --quiet) or --format terse. We could just keep --format terse but I think -q is convenient (and format is more general as it will soon support json).

Here's the output when all tests pass:

Additional Context

1. The proptest output that shows up in the middle of the run will be gone with fix: disable failure persistance in nargo test fuzzing #6777
2. I just noticed that we have duplicate and now outdated code to run stdlib tests here. We've been able to run nargo test inside noir_stdlib for a while now so we can probably move those to a CI test matrix (in this PR I tried to reuse the code from nargo_cli but I couldn't because nargo_cli is a binary and we can't use that binary as a dependency in test integrations).

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.

[github-actions]

Compilation Sample

Program	Compilation Time	%
sha256_regression	0m1.439s	-4%
regression_4709	0m0.737s	-6%
ram_blowup_regression	0m17.030s	1%
private-kernel-tail	0m1.292s	7%
private-kernel-reset	0m9.348s	1%
private-kernel-inner	0m2.803s	10%
parity-root	0m1.166s	33%
noir-contracts	2m45.216s	-1%

[github-actions]

Peak Memory Sample

Program	Peak Memory
keccak256	79.14M
workspace	122.04M
regression_4709	295.98M
ram_blowup_regression	2.44G
private-kernel-tail	210.43M
private-kernel-reset	862.21M
private-kernel-inner	307.94M
parity-root	175.78M

[aakoshh]

Awesome, nice to see it broken up!

[aakoshh]

It would be nice to change this to contain the path like this one does.

Curiously even though it fails on another PR that one has a green status. Maybe we don't want to be blocked by other repos checking in broken code?

[asterite]

It would be nice to change this to contain the path like this one does.

Done!