Track various compiler settings in benchmarking reports

[vezenovm]

Problem

We have several reports in CI for tracking compilation/execution times as well as their peak memory usage.

These reports currently do the most basic nargo compile --force and nargo execute.

We have important compiler flags whose settings we should also check. For example, noir-contracts are compiled with --inliner-aggressiveness 0, but our default is i64::MAX.

Happy Case

We should benchmark the compiler with critical settings.

To start, the most important ones to test would be variations of inliner aggressiveness when force compiling to Brillig.

We already test compiling and executing with our defaults. We should also check the following:

--inliner-aggressiveness i64::MAX (default)
--inliner-aggressiveness 0
--inliner-aggressiveness i64::MIN

We probably can test these all with --force-brillig as that is when the inliner actually can vary in its aggressiveness and will be enough to give us a picture of what is happening with the compiler.

Workaround

Yes

Workaround Description

Test manually

Additional Context

No response

Project Impact

Nice-to-have

Blocker Context

No response

Would you like to submit a PR for this Issue?

None

Support Needs

No response