fix(pretty-format): handles jsdom attributes properly

[pikou1995]

Summary

fixes #10770.

expect(received).toMatchObject(expected)

When received object mismatch with expected object, jest will copy received object withdeepCyclicCopyObject.

As for this issue, received object contains jsdom provided objects AbortController, and will encounter jsdom/lib/jsdom/living/attributes.

This module also contains hasAttribute, prettyFormat.plugins.DOMElement.test will throw an exception by calling hasAttribute.

Test plan

added handles jsdom attributes properly test.

[netlify]

Deploy preview for jestjs ready!

Built without sensitive environment variables with commit d9eee82

https://deploy-preview-11189--jestjs.netlify.app

[codecov-io]

Codecov Report

Merging #11189 (d9eee82) into master (f73d5f6) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master   #11189      +/-   ##
==========================================
- Coverage   64.14%   64.14%   -0.01%     
==========================================
  Files         307      307              
  Lines       13375    13379       +4     
  Branches     3260     3261       +1     
==========================================
+ Hits         8580     8582       +2     
- Misses       4089     4090       +1     
- Partials      706      707       +1     

Impacted Files	Coverage Δ
packages/pretty-format/src/plugins/DOMElement.ts	97.22% <100.00%> (+0.34%)	⬆️
packages/expect/src/utils.ts	94.83% <0.00%> (-1.30%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f73d5f6...d9eee82. Read the comment docs.

[jeysal]

I don't really understand how AbortController plays into encountering this and thus why the test added is exactly the way it is, but either way catch when calling unknown functions that could do anything is the right thing to do 👍

[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.