fix(expect): fix toEqual and toMatchObject with circular references

[hi-ogawa]

Description

• closes Cannot test object with multiple circular references #5533
• closes RangeError: Maximum call stack size exceeded when toMatchObject with array circular references #5538

This seems to be a regression from custom equality tester #4880 (introduced in v1.2.0). I haven't properly analyzed code, but this filteredCustomTesters looks fishy.

Btw, it turned out it reproduces on Jest too since code looks mostly same https://github.com/hi-ogawa/reproductions/tree/main/jest-circular-iterable

Searching Jest issues, I found a similar issue and this reproduces on Vitest jestjs/jest#14734. They seemed to fixed this one already, so I'll try port back to Vitest later.
(EDIT: this one is also partially fixed)

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	c2274b6
🔍 Latest deploy log	https://app.netlify.com/sites/fastidious-cascaron-4ded94/deploys/661e4f86f42ff60008738b27

[hi-ogawa]

I'm not sure if this fix is entirely fool-proof for more complicated case, but at least this recursion with filteredCustomTesters seems redundant.

Previously iterableEqualityWithStack was calling iterableEquality(..., [... iterableEqualityWithStack], ...), but iterableEquality is already setting up filteredCustomTesters.
(I don't know how to explain this better...)

[hi-ogawa]

I haven't follow up this properly, but in some cases, utils.getMessage also gets in loop (stacktrace shows loupe is doing something).

For now, I hid it inside failure case since msg is not used fro success case anyways.

[hi-ogawa]

I'm not entirely convinced with the fix for subsetEquality as well, but the "array" specific infinite recursion is due to seenReference is missing array.

(Actually I'm fine with the fix, but I feel the implementation of subsetEquality feels a little off in general since it doesn't take the approach of aStack/bStack like eq and iterableEquality do)