feat: Add full call stacks to runtime errors

[jfecher]

Description

Problem*

Resolves #2214

Summary*

Adds full call stacks to runtime errors. I'll update this PR when it is ready to be merged with examples of what the new errors look like.

Documentation

• This PR requires documentation updates when merged.

  • I will submit a noir-lang/docs PR.
  • I will request for and support Dev Rel's help in documenting this PR.

Additional Context

PR Checklist*

• I have tested the changes locally.
• I have formatted the changes with Prettier and/or cargo fmt on default settings.

[jfecher]

I have a local commit that changes the errors to format as part of one error:

error: Failed constraint
   ┌─ /.../noir/short/src/main.nr:17:12
   │
17 │     assert(x == 246);
   │            --------
   │
   = Call stack:
     1. /.../noir/short/src/main
     2. /.../noir/short/src/main

But the issue is in generating the call stack string. Once codespan no longer handles the error spans, we have no way of converting the byte start and end offsets into line and column numbers. I'll push a commit tomorrow to add these by manually recounting them from the file contents.

[jfecher]

This PR is now ready to review. The final formatting I've settled on is:

error: Failed constraint
   ┌─ /.../noir/short/src/main.nr:17:12
   │
17 │     assert(x == 246);
   │            --------
   │
   = Call stack:
     1. /.../noir/short/src/main.nr:9:5
     2. /.../noir/short/src/main.nr:13:5
     3. /.../noir/short/src/main.nr:17:12

Error: could not satisfy all constraints

In the future, we should add function names to each location as well.

[kevaundray]

Generally looks good to me; I had one nit regarding interchangeably using callstack and location

[Ethan-000]

should "unoptimized" be added to the spell checker. couple of places seems to be using this word