Split out Jest preset to @react-native/jest-preset

[kitten]

Summary:

This implements the proposal to split the Jest preset (and dependencies) out into a separate package: react-native-community/discussions-and-proposals#926

• react-native has an optional peer dependency on @react-native/jest-preset
• react-native/jest-preset.js throws when @react-native/jest-preset isn't installed and instructs the user to add it to migrate
• @react-native/jest-preset may be used directly as a Jest preset

Changelog:

[GENERAL] [BREAKING] - Move Jest preset to new @react-native/jest-preset package

Test Plan:

The jest preset is used, with some modifications, in facebook/react-native itself and CI should confirm that the changes work. Running jest on the repo similarly validates that the preset still works.

Otherwise, nothing has changed and the easiest way to test this is to use the preset in an existing project and try both preset set to the current value and preset set to "@react-native/jest-preset"

[huntie]

Thanks for this great README ❤️

[huntie]

quick nit: Can we use packages/jest-preset/ as the dir name? (I appreciate we aren't consistently one way or the other yet!)

[meta-codesync]

@huntie has imported this pull request. If you are a Meta employee, you can view this in D91700684.

[huntie]

@kitten I'm debating about whether this counts as a deprecation, since we'll throw a hard error here.

• I'd recommend we rephrase this to "has moved" — since the migration path is so straightforward. Move Fast.
• If we want to keep "is deprecated", we should consider depending on the subpackage for one release so that this only warns.

cc @cortinico @cipolleschi

[huntie]

Incoming replacement copy:

     throw new Error(
      `The React Native Jest preset has moved to a separate package.
To migrate, please install "@react-native/jest-preset" and update your
jest.config.js to reference:
  preset: '@react-native/jest-preset'`,
    );

The config reference remains deprecated (and I'm leaving this wording in the new package README), but we're communicating the direct migration path for the breaking change here to the user in one go.