Document the noir-profiler

[vezenovm]

Problem

A few months ago we added a profiler under tooling/profiler. The profiler has been used almost exclusively internally. This profiler allows devs generate flamegraphs of the opcodes and backend constraints laid down by a given program. Just recently the profiler was expanded to also provide information on which part of the program is generated the most steps in the Brillig VM.

Happy Case

We should document the profiler inside the Noir repo and externally to allow developers to start to utilize this very useful tool.

Workaround

None

Workaround Description

No response

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