feat: stringify Errors properly with --json flag

[tonyd33]

Summary

When running jest with the --json flag, the Errors from collectHandles in jest-core/src/runJest.ts is all passed into a JSON.stringify, which turns them into an empty object.

Users might expect or want the error message, name, and stack from the --json output possibly to collect data in the more structured JSON format — as opposed to plain stderr output — to help diagnose the source of the leaky handles.

Changes

Originally, I just iterated over the runResults.openHandles in runJest.ts:processResults to grab the error message, name, and stack from the Error, but adding a test for that was kind of awkward.

So I decided on adding a very basic serializeToJSON function that should replace JSON.stringify to handle stringifying Errors as well as leaving room to stringify other objects in the future if needed.

Test plan

• Added tests for serializeToJSON
  • Check that it's the same as JSON.stringify for regular objects
  • Check that it extends JSON.stringify by stringifying Errors properly

For a more e2e test, I added a temporary test to leak a handle, built the project, and ran the test:

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: tonyd33 / name: Tony (5f85233, 2cbba58)
• ✅ login: SimenB / name: Simen Bekkhus (7877115, 5caff62, 24bd16d, 59cf055)

[netlify]

✅ Deploy Preview for jestjs ready!

Name	Link
🔨 Latest commit	7877115
🔍 Latest deploy log	https://app.netlify.com/sites/jestjs/deploys/6787ab225a0ca600080ec558
😎 Deploy Preview	https://deploy-preview-15329--jestjs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

This PR is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[SimenB]

thanks!