fix: not addressing to Sets and Maps as object without keys

[ofekm97]

Summary

Fixes #14599
The problem is that comparing list of nulls with Set or list of Sets:

expect([null]).toMatchObject([new Set()]);
expect([null]).toMatchObject(new Set());

In both cases the comparison does not throw an exception.

---

Update:
Same issue is happening with Map instead of set, I have fixed it too

expect([null]).toMatchObject([new Map()]);
expect([null]).toMatchObject(new Map());

Test plan

Unit tests added
Both cases described in the Summery have been tested locally with the fix and reproduced without the fix

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: ofekm97 / name: Ofek Meoded (f2346a7)
• ✅ login: SimenB / name: Simen Bekkhus (ae8284e)

[netlify]

✅ Deploy Preview for jestjs ready!

Name	Link
🔨 Latest commit	ae8284e
🔍 Latest deploy log	https://app.netlify.com/sites/jestjs/deploys/6627f0cb8cb00600097fce10
😎 Deploy Preview	https://deploy-preview-14873--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.

[ofekm97]

In case of subset as a Set the getObjectKeys(subset) at line 358 returns empty array ([]), so the .every(...) in the same line is vacuous truth, resulting the comparison not to raise an exception

[SimenB]

Thanks!

[ofekm97]

@SimenB Hey, I see one of the tests failed after the squash - is there an option to rerun it only? 🙌

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.