[Bug]: matcher error is not shown when the expected object has throwing getter

[rluvaton]

Version

29.7.0

Steps to reproduce

Repro - CodeSandbox

Run this:

const obj = {
  get deprecatedFunction() {
    throw new Error('custom')
  }
}

test('Playground', () => {
  expect(obj).toEqual({
    a: expect.objectContaining({})
  })
});

Expected behavior

The matcher error should be thrown:

expect(received).toEqual(expected) // deep equality

- Expected  - 0
+ Received  + 1

  Object {
    "a": ObjectContaining {},
+   "deprecatedFunction": undefined,
  }

   5 | }
   7 | test('Playground', () => {
>  8 |   expect(obj).toEqual({
     |               ^
   9 |     a: expect.objectContaining({})
  10 |   })
  11 | });

Actual behavior

The error custom was thrown making it impossible to know what was wrong

● › Playground
custom

   5 | }
   7 | test('Playground', () => {
>  8 |   expect(obj).toEqual({
     |               ^
   9 |     a: expect.objectContaining({})
  10 |   })
  11 | });

Additional context

I'm writing custom expect matchers that add assertions for HTTP response objects, and the got library has:

    get searchParameters() {
        throw new Error('The `searchParameters` option does not exist. Use `searchParams` instead.');
    }

in the response and I can't test my matcher error output message

This happens here:

jest/packages/jest-matcher-utils/src/deepCyclicCopyReplaceable.ts

Lines 105 to 107 in bd1c6db

	// this accesses the value or getter, depending. We just care about the value anyways, and this allows us to not mess with accessors
	// it has the side effect of invoking the getter here though, rather than copying it over
	(object as Record<string | symbol, unknown>)[key],

I don't think that stringify should throw

Environment

System:
    OS: macOS 14.6.1
    CPU: (10) arm64 Apple M1 Max
  Binaries:
    Node: 22.3.0 - ...
    npm: 8.19.4 - ...