fix: match jest json output by providing full stack trace

[bard]

Description

Continuation of #4826.

Jest's JSON output reports the full stack trace in the failureMessage field. This PR aligns Vitest's JSON reporter output to Jest's in that regard.

Note: not sure what's causing the conflict on the snapshot, I can't seem to reproduce it locally.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[netlify]

✅ Deploy Preview for fastidious-cascaron-4ded94 canceled.

Name	Link
🔨 Latest commit	a366cc0
🔍 Latest deploy log	https://app.netlify.com/sites/fastidious-cascaron-4ded94/deploys/659311c7083ec50008fc4c5f

[sheremet-va]

You can't reproduce it locally because the file paths in stack traces lead to files on your PC, not CI's 😄

[bard]

You can't reproduce it locally because the file paths in stack traces lead to files on your PC, not CI's 😄

Hmm, that is the case on json.test.ts.snap, but the conflict is reported to be on reporters.spec.ts.snap.

Still, it's a problem on json.test.ts.snap. Not sure how to handle it though.

[hi-ogawa]

Still, it's a problem on json.test.ts.snap. Not sure how to handle it though.

I don't think it's necessary to snapshot the whole "stack" string? How about moving out the part of the assertion and do it manually like this?

    expect(result.failureMessages[0]).toMatch(
      /^AssertionError: expected 2 to deeply equal 1\n.*json-fail.test.ts:8:13/);
    result.failureMessages = [];

vitest/test/reporters/tests/json.test.ts

Line 19 in 70e8a38

expect(result).toMatchSnapshot()

[sheremet-va]

This should be fixed by #5434 in the next major version.