Terminal escape codes in test output

[nobleach]

I'm running the Vitest adapter, and I'm noticing terminal escape codes in the output:

This happens when there's a warning. I've dug around a bit but I'm still not sure where the stdout/stderr is handled before being piped into the popup window. Otherwise, I'd love to submit a PR instead of just an issue.

This is what I get when I run the same test directly from the command line:

[quolpr]

@nobleach thanks for the report! Yep, it's annoying, will fix it soon.