Revert Jest upgrade

[JPeer264]

revert #3201 and #3191 because releasing won't work with this update.

[github-actions]

	Fails
🚫	Please consider adding a changelog entry for the next release.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

### Features

- Revert Jest upgrade ([#3202](https://github.com/getsentry/sentry-cli/pull/3202))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description or adding a skip-changelog label.

Generated by 🚫 dangerJS against afb79da

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Jest config in package.json silently ignored by jest.config.js

High Severity

The "jest" configuration block added to package.json (collectCoverage, testEnvironment, testPathIgnorePatterns) is silently ignored because jest.config.js exists. Jest uses jest.config.js as the sole configuration source when present. This means collectCoverage won't be enabled, testEnvironment will default to "jsdom" (Jest 27's default) instead of "node", and the testPathIgnorePatterns from package.json won't apply. The testEnvironment mismatch is especially likely to cause test failures since Node-specific APIs won't be available under jsdom.

Additional Locations (1)

• jest.config.js#L1-L7

 

[cursor]

Integration test ignore pattern silently dropped from config

Medium Severity

The testPathIgnorePatterns entry for '<rootDir>/tests/integration/' was removed from jest.config.js and not restored anywhere in the effective configuration. Integration tests that were previously excluded from the default test run will now execute, potentially causing unexpected failures or slowdowns in the regular test suite.

 

[JPeer264]

closed in favor in favor of #3194