feat(profiler): Add Brillig procedure info to debug artifact for more informative profiling

[vezenovm]

Description

Problem*

Resolves

Part of general effort to reduce the Brillig execution trace.

Summary*

In #6253 we added a command to the noir profiler that allows us to generate a flamegraph of the opcodes executed by the VM. However, the current debug metadata on its own does not provide a full picture. We have reusable procedures in Brillig for common operations such as mem copy, array copy, checking the max stack depth, etc. As procedures are themselves made up of multiple lower level opcodes procedures are executed in a similar way to other calls. This makes it difficult to discern which opcodes come from these common reusable procedures.

This PR adds a mapping of procedure ids to the range of opcodes that they occupy inside of a Brillig artifact.

The sha256_regression test from master:

Here is an example of the sha256_regression test:

You can see how multiple opcodes with previously unknown locations are now associated with a mem copy procedure (in fact it is 15% of the entire program, which in itself provides us with some valuable insights that can be addressed in optimization follow-ups).

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.

[asterite]

Looks good! I left a few minor comments.