Output debug files for external trazability of errors

[sirasistant]

Problem

Right now only nargo can figure out during execution which assertion errored. This is due to the fact that we are collecting debug info during compilation and using it in nargo execute, but never outputting it for external usage.

Happy Case

A new compile flag that outputs debug info along with a file map that allows resolving the locations in the debug info.

Alternatives Considered

Instead of attaching the file map, pre resolving the locations in debug info. This has been superceded by embedding the source of the file since it can improve debugging tools.

Additional Context

No response

Would you like to submit a PR for this Issue?

Yes

Support Needs

No response