Update Jest config to avoid transpiling dependencies

[Mrtenz]

By default Jest looks at the module field of a package before looking at main. The module field is often used for the ESM version of a package, which is not supported by our configuration.

Previously we solved this by transpiling all dependencies that had this issue. In this PR I changed it to only look at main, which is usually the CJS version of a package. This removes the need for transpiling dependencies, and could speed up the tests slightly.

I also bumped Jest to a stable (non-alpha) version of 29.

[metamaskbot]

Builds ready [f0e0bb4]

• builds: chrome, firefox, opera
• builds (beta): chrome, firefox, opera
• builds (flask): chrome, firefox, opera
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6, 7
  • common: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9
  • content-script: 0
  • contentscript: contentscript
  • disable-console: disable-console
  • inpage: inpage
  • policy-load: policy-load
  • sentry-install: sentry-install
  • ui: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (2521 ± 240 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	98	188	126	24	12
		domContentLoaded	1790	3388	2497	494	237
		load	1790	3388	2521	500	240
		domInteractive	1790	3388	2497	494	237

[brad-decker]

Niiice.