Revert "feat(testing): update jest to v29.6.1 (#18061)"

[barbados-clemens]

This reverts commit 90172c5.

Current Behavior

jest v29.6.1 appears to be having a memory leak of some kinds causing CI to crash with OOM when testing angular

Expected Behavior

nx own tests should not start failing in CI with jest version bumps

Related Issue(s)

maybe related:
jestjs/jest#14042

some extra notes while investigating:

1. seems like tests that contain more imports that require transformations use more memory (obviously), but that memory is never freed. it just keeps growing. I would expect it to start going down after the transformed code is consumed and saved to cache?
2. --detectLeaks (beta feature of jest) shows ever test has a leak, so maybe something there in our code setup might be doing something weird?
3. did not see anything with --detectOpenHandles for the angular tests
4. switching to another transformer (swc/jest) required refactoring all tests with mocks to make sure the import order is loading correctly (about 150 tests) but even when those tests weren't running heap usage was around 2 GB, when CI was dying around 1.8 GB (locally with ts-jest showing 2.8-3 GB of memory usage) and those last 150 tests might still reach the same usage?
5. usage of jest v29.4.3 is around 800MB with a spike around 2GB (then drops back down pretty quick)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 12, 2023 9:21pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 5cc7bd2. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 1 target

• nx affected -t e2e-macos --parallel=1 --base=77bb4b7429ac0c011afeb684b265662b25ae3d19 --head=5cc7bd23d276fbaddf198a0498cca883bbfba14d

---

Sent with 💌 from NxCloud.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.