chore: Update Jest to v29

[legobeat]

This is #7160 rebased on main with changes to snapshots reapplied

---

Jest has been updated to v29, along with related dependencies. This change comes with a number of new features, such as the new jest.replaceProperty() function.

The only breaking change affecting us is a change to the snapshot format. All snapshots have been updated.

See here for the migration guide: https://jest-archive-august-2023.netlify.app/docs/upgrading-to-jest29/

See here for a full list of changes: https://github.com/jestjs/jest/blob/main/CHANGELOG.md#2900

Description

Related issues

Blocked by

• chore(devDeps): bump @babel/core to ^7.24.5 #9459

Blocking

• chore: upgrade nodejs from ~18.18.2 to ^18.20.2 #9452

Previously

• chore: Update Jest to v29 #7160
• Research jest v29 with React 18 #6277
• chore: Update Jest to v28 #6876
• chore: set nvmrc to 18.18.2 #8960

Manual testing steps

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@types/jest@29.5.12	Transitive: environment	+4	564 kB	types
npm/babel-jest@29.7.0	environment Transitive: eval, filesystem, network, shell, unsafe	+37	1.15 MB	simenb
npm/expect@29.7.0	Transitive: environment, unsafe	+16	903 kB	simenb
npm/jest-matcher-utils@29.7.0	None	+5	563 kB	simenb
npm/jest@29.7.0	Transitive: environment, eval, filesystem, network, shell, unsafe	+103	3.65 MB	simenb

🚮 Removed packages: npm/@types/jest@28.1.8, npm/babel-jest@28.1.3, npm/jest@28.1.3

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/create-jest@29.7.0

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[legobeat]

@SocketSecurity ignore npm/create-jest@29.7.0

new author ok

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[Gudahtt]

LGTM!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[Cal-L]

Code LGTM, let's wait until e2e passes to merge

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: e34768d
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/81d18c1d-ba85-49c0-a43b-85c1731bede8

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request