chore: Update memory report to run noir-contracts repo

[vezenovm]

Description

Problem*

Resolves #6883

Summary*

I just saw #6807 and noticed that ram_blowup_regression went down by 50%. I remembered that this is a pattern common in the noir contracts so I want to test bringing back the noir-contracts repo to the memory report. Previously it took just under 30 minutes and had a peak memory of ~9 GB.

After #6875 the report now finishes in the CI report. It finishes in ~28 minutes.

Additional Context

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	1.460s	1%
regression_4709	0.829s	0%
ram_blowup_regression	16.051s	-1%
rollup-base-public	127.104s	-6%
rollup-base-private	108.413s	-4%
private-kernel-tail	1.121s	6%
private-kernel-reset	8.324s	1%
private-kernel-inner	2.309s	3%
parity-root	0.733s	-5%
noir-contracts	91.986s	-1%

[github-actions]

Peak Memory Sample

Program	Peak Memory
keccak256	78.56M
workspace	123.34M
regression_4709	423.67M
ram_blowup_regression	1.58G
private-kernel-tail	207.23M
private-kernel-reset	720.82M
private-kernel-inner	292.44M
parity-root	172.24M
noir-contracts	6.49G

[vezenovm]

Ok looks like the noir-contracts memory report still did not finish

[github-actions]

Execution Sample

Program	Execution Time	%
sha256_regression	0.628s	0%
regression_4709	0.395s	0%
ram_blowup_regression	4.375s	-1%
rollup-base-public	21.249s	0%
rollup-base-private	19.189s	0%
private-kernel-tail	0.698s	-3%
private-kernel-reset	1.495s	0%
private-kernel-inner	0.973s	1%
parity-root	0.523s	-4%

[vezenovm]

It still takes about 28 minutes to generate the report @TomAFrench. Not sure if we want to merge this to run like every other report. If we do, then this report will become the bottleneck for CI.

[TomAFrench]

Yeah I agree 28 minutes is too much.

[TomAFrench]

We may want to pull out a couple of contracts in particular that are interesting but running a whole workspace is a waste of time.

[TomAFrench]

Closing this PR as I've updated the issue with the extra context on CI times.