feat(babel-preset-expo): auto add reanimated babel plugin when available

[EvanBacon]

Why

One less thing to think about. However, installing the package would mean you need to magically know about invalidating the Metro Babel cache. To account for this the expo/metro-config will now auto-invalidate when the reanimated version changes. This invalidation also solves another common issue where the worklet format changes between versions.

Test Plan

• Added a babel test to ensure duplicates don't break the worklet format.
• Manually tested by packing babel-preset-expo and installing a tabs@49 template. If you install react-native-reanimated, then restart the server, worklets will be transpiled.

Checklist

• Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
• Conforms with the Documentation Writing Style Guide
• This diff will work correctly for npx expo prebuild & EAS Build (eg: updated a module plugin).

[ide]

Is there ever a case where it is necessary to opt-out without removing react-native-reanimated, such as in a monorepo where another workspace package depends on react-native-reanimated?

[EvanBacon]

@ide users can pass reanimated: false to disable the feature. The reanimated plugin will add time, but it seemingly doesn't do anything unless the reanimated syntax is used. I would imagine that no one else is using "worklet" directives in the ecosystem.

[brentvatne]

we should probably add something here to indicate that you can remove the reanimated babel plugin that we automatically add, and link to the babel-preset-expo readme or docs for that