Improve error recovery

[natemoo-re]

Changes

• This adds some logic to intercept and format panics so that we actually reject the transform promise with the correct error instead of just printing the error to stdout.
• Trims irrelevant info from the stacktrace and formats to more helpful internal file location.
• Formats errors similarly to JS stacktraces so that they don't confuse users
• Related to Remove legacy compiler error handling astro#5855

Testing

Tested manually

Before	After

Docs

N/A, QoL improvement

[changeset-bot]

🦋 Changeset detected

Latest commit: fe86fa9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@astrojs/compiler	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[Princesseuh]

I'm not sure how I feel about the stacktrace being JS like. Even though those are nicer than Go's, I feel like modifying "technical" information can lead to more problems unnecessarily. Sure, they don't scare users as much, but someone used to Go's stacktraces will just find it weird (+ I'm guessing you can't CTRL+click them like you'd do with JS's)

[natemoo-re]

Alright, thanks for the comments! After thinking about it, I totally agree that transforming the stacktraces is probably going to cause more issues than it will help, so I've removed that logic in c584433.

[Princesseuh]

Looks amazing, so nice to see the error in the new overlay!