feat: Implement Noir debugger (brillig)

[dmvict]

Description

The separate binary app to debug noir binary applications using brillig bytecode.

Problem*

It's new feature.
The related issue is #3094

Summary*

Extends Noir toolings by the new utility. Allows to compile brillig bytecode for a noir binary module and debug it.

Additional Context

Documentation*

Check one:

• No documentation needed.
• Documentation included in this PR.
• [Exceptional Case] 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.

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
@types/glob	8.1.0	None	+2	3.8 MB	types
esbuild	0.18.20	environment	+22	207 MB	evanw
@types/mocha	10.0.4	None	+0	95.4 kB	types
@types/vscode	1.84.1	None	+0	626 kB	types
@typescript-eslint/eslint-plugin	5.62.0	None	+17	48.7 MB	jameshenry
@typescript-eslint/parser	5.62.0	None	+10	45.5 MB	jameshenry
@types/node	20.2.5	None	+0	3.78 MB	types
@vscode/test-electron	2.3.6	eval, filesystem, shell, environment	+5	939 kB	vscode-bot
eslint	8.53.0	None	+3	3.14 MB	eslintbot
typescript	5.2.2	None	+0	40.6 MB	typescript-bot

[dmvict]

I made no changes in the main parts of code but I'll check the failed workflows.
Please, see updates in #3094

[kevaundray]

Does this still need to use a fork?

[dmvict]

Does this still need to use a fork?

Hello @kevaundray

Yes, the pr still need the fork. I described the changes in the first post in the issue #3094.
Here is the code that allows to compile the brillig bytecode.
I think we should continue discussion about integration of this changes in the other issue/pr.
Once the changes will be properly integrated into repo I'll be able to remove the fork from dependencies.