[jest] switch to jest-environment-jsdom

[spalger]

In #58095 we switched to the jest-environment-jsdom-thirteen package because at the time Jest was stuck on version 11 of JSDOM, they have since upgraded their version and we can now switch back over to the standard jest-environment-jsdom package which includes several other new features (like the "modern" timer mocks).

[spalger]

@elasticmachine merge upstream

[spalger]

Bunch of test timouts in the first CI run https://kibana-ci.elastic.co/job/elastic+kibana+pipeline-pull-request/114461/testReport/

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: e2a7c20
• Storybooks Preview

Metrics [docs]

✅ unchanged

History

• 💔 Build #114478 failed d0e01aa
• 💔 Build #114474 failed 44d8da7
• 💔 Build #114461 failed 86c3211

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[joshdover]

These global_search failures seem like something, no? That test is explicitly testing which element is the active focus element and the results are now different when using the other jsdom. Seems potentially problematic for any a11y related tests in the future.

[spalger]

These global_search failures seem like something, no? That test is explicitly testing which element is the active focus element and the results are now different when using the other jsdom. Seems potentially problematic for any a11y related tests in the future.

I imagine it's possible that newer versions of JSDOM support a different amount of a11y interactions, maybe more or less, but I'm not sure and that's why those tests have been pinned to JSDOM 13. I think it's up to people who understand the test better to figure out if they can or should upgrade to a more modern version of JSDOM. I expect that JSDOM better emulates browsers in more modern versions, so maybe it's an actual issue with the component that the tests weren't able to test for before, or maybe there were special accommodations added for the way JSDOM 13 worked... Could be a lot of things I think.

[wylieconlon]

LGTM, thanks for opening team-specific issues

[kibanamachine]

💚 Backport successful

✅ 7.x / #95326

This backport PR will be merged automatically after passing CI.