chore(testbed): jest 29, flakiness fixes

[kanadgupta]

🧰 Changes

This PR bumps Jest and handles a bunch of testbed housekeeping. Not sure if tests are faster¹, but the flakiness when running them locally should be gone.

• Bumped jest, ts-jest, and @types/jest to v29² and updated snapshots accordingly (see their blog post) 🆙 📸
• It was always bugging me that we had set our NODE_ENV value to testing for our testing environment as opposed to the widely used NODE_ENV value of test, so this makes that long overdue change. We were able to make a slight cleanup to our setup file as a result. 🧹
• configstore has continued to give us grief when running tests locally and I had the idea of including the JEST_WORKER_ID in our configstore paths so Jest workers aren't clashing with each other. Now the test bed is editing a few of config files (7 on my local machine) instead of just one. That tiny change completely solved the flakiness on my local machine ✨

Sadly, our Jest coverage issues in CI (see #617) continue to persist 😭

🧬 QA & Testing

Do tests pass? And do they always pass?

Footnotes

1. I mean... tests do feel faster? But maybe that's just a placebo ¯_(ツ)_/¯ ↩

2. We were struggling to upgrade to Jest 29 for a few weeks now since our __tests__/tsconfig.json file wasn't being read properly. After noodling on this for a bit, I discovered that bumping us down to the legacy ts-jest preset fixed everything :cryparty: I don't love this solution but hopefully it's temporary. ↩

[erunion]

glad you were able to finally sort this out