refactor(cli/fmt_errors): Format stack frames in prepareStackTrace()

[nayeemrmn]

Ref #4690 (comment), cc @ry @piscisaureus.

This implements the coloring in prepareStackTrace() and passes the formatted strings to Rust via error.__formattedFrames.

Since the formatting in prepareStackTrace() is properly aligned with V8, this fixes 1/3 and 2/3 of #4705. 3/3 (which involves a built-in function frame) requires making line and column numbers optional in Rust and then just removing the null guard, I'll see about that later.

The source line formatting is still duplicated in core/js_error.rs and cli/fmt_errors.rs.

[kitsonk]

I know it isn't directly related to this, but we should start using std/fmt/colors.ts instead of the js/colors.ts and get rid of it. It is a hold over from when it was difficult/impossible to use std in internal Deno code.

[ry]

We still don't have any imports from core into std. Hopefully it would work easily - but I wouldn't be surprised if there were unexpected difficulties.

[ry]

Sometimes we have exception objects in Rust and want to print them. Doesn't this make it so we can only print exceptions from JS?

Also seems to remove tests...

[nayeemrmn]

Sometimes we have exception objects in Rust and want to print them. Doesn't this make it so we can only print exceptions from JS?

How so? The whole point is to pass the formatted string from JS to Rust. The impl fmt::Display for JSError is still there and has the same kind of output.

Also seems to remove tests...

Yeah, some functionality was moved from those modules to error_stack.ts. error_stack_test.ts already has tests for source mapping, I need to add another to replace the two to_string tests I removed and that should suffice. Although I guess that's well covered in the integration tests... but the #4705 cases need tests.

[ry]

LGTM