chore(ui): Change testEnvironment from node to jsdom

[rpelczar]

Tests in some PRs failed because the testEnvironment option was set incorrectly. I have no idea why the tests sometimes passed. This change should fix that.

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• Optional. My organization is added to USERS.md.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (58da6a3) 49.51% compared to head (a7284f2) 49.52%.
Report is 3 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #16287   +/-   ##
=======================================
  Coverage   49.51%   49.52%           
=======================================
  Files         269      269           
  Lines       46990    46990           
=======================================
+ Hits        23269    23272    +3     
+ Misses      21437    21435    -2     
+ Partials     2284     2283    -1     

see 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[matthewhughes-uw]

Thanks for this! I was wondering why these tests were failing in CI for my non-UI change.

I have no idea why the tests sometimes passed. This change should fix that.

This was also confusing me. For what it's worth I can reproduce this failure everytime locally if I run yarn test --no-cache however with caching it will fail the first time and then succeed every time after that. So if CI was storing jest's cache I guess this could explain it sometimes failing and sometimes not.

[alexmt]

Thank you!