Improve error experience in run mode and open mode

[brian-mann]

What would you like?

• Many errors are incorrectly constructed when user code is involved, which obfuscates the stack trace
• Most newer errors have inconsistent and arbitrary styling and formatting
• Errors propagated in the desktop GUI are rendered incorrectly
• ANSI styles are not always stripped from the stacks
• Many stack traces are flat out wrong
• There are multiple stack traces rendered (from the original error and the internally handled cypress error)
• Errors are backticked in stdout for use in markdown, instead of being ANSI styled
• Errors originating from user code in the desktop-gui hide the most important detail (the stack trace) and require "opening" the error details - while the Stack Trace details button repeats the same wrapped error and offers zero benefit

Examples (not exhaustive)

Hidden stacks from user code - with the details of the message only showing in the expanded stack

Duplicate stacks - one from the constructed error, one from the user error

ANSI styles not stripped, showing up in stack traces

Backticks, backticks, backticks formatting

General formatting and readability

Why is this needed?

No response

Other

No response

[cypress-bot]

Released in 9.5.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v9.5.0, please open a new issue.