fix(debugger): improve output when assertion fails in Brillig

[anaPerezGhiglia]

Description

When an assertion fails on Brillig mode, the debugger fails to indicate the user where the program failed

while when running on ACIR mode it provides enough information

Problem*

Resolves

Summary*

• assert constraints are translated as "jump to trap" if the condition is not met when running in Brillig mode
• Solution: treat FailureReason::Trap specifically when handling brillig vm status. Treat these failures as an OpcodeResolutionError::UnsatisfiedConstrain instead of an OpcodeResolutionError::BrilligFunctionFailed
  • By doing these, the error will be reported the same way as when running in ACIR mode

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]

Thank you for your contribution to the Noir language.

Please do not force push to this branch after the Noir team have started review of this PR. Doing so will only delay us merging your PR as we will need to start the review process from scratch.

Thanks for your understanding.

[anaPerezGhiglia]

Closing this PR since these changes make nargo tests to fail.