fix: do not pass unsafe matcherResult over IPC

[yury-s]

Fixes #35562

[yury-s]

Note that it changes the error message of expect(1).toBe(() => {}); from

Expected: [Function anonymous]

to

Error: () => {} could not be cloned.

We do need to throw on serialization errors, but I'm not sure if we want to do the switch to structured clone.

[dgozman]

I'd prefer our IPC to be pure json. Are these the expected/actual values? Perhaps we can apply our utility script serializer to them?

[yury-s]

Are these the expected/actual values?

In this case yes. It's the actual value (probably formatted by expect matcher).

[github-actions]

Test results for "tests 1"

4 flaky

⚠️ [firefox-library] › library/inspector/cli-codegen-pick-locator.spec.ts:35:7 › should update locator highlight @firefox-ubuntu-22.04-node18
⚠️ [firefox-page] › page/page-evaluate.spec.ts:424:3 › should throw for too deep reference chain @firefox-ubuntu-22.04-node18
⚠️ [chromium] › headerView.spec.tsx:46:1 › should toggle filters @web-components-html-reporter
⚠️ [webkit-page] › page/elementhandle-bounding-box.spec.ts:22:3 › should work @webkit-ubuntu-22.04-node18

39131 passed, 806 skipped
✔️✔️✔️

Merge workflow run.