Create Config Plugins

[EvanBacon]

Config plugins are a system for configuring native modules automatically during the "prebuild" step. In order to make managed projects work with eas build we need expo-cli to be able to automatically apply config plugins in managed packages and apply them.

The majority of the required plugins are added in #11538 along with a test project native-component-list.

Remaining Plugins

The following plugins still need to be created before we can automatically configure all managed libraries in the Expo SDK during expo prebuild.

Duplicates

These will be (more or less) automatically configured in expo-cli, but we need to create versioned copies. Ideally these would come over after we think up a good strategy for using TypeScript for plugins and testing (because they're already in TS in expo-cli).

• expo-facebook - created expo-facebook plugin #11624
• expo-branch - created expo-branch plugin #11623
• expo-notifications - created expo-notifications plugin #11633
• expo-splash-screen - created splash-screen plugin #11634
• expo-ads-admob - created ads-admob plugin #11636
• expo-updates - [expo-updates] Created config plugin #11981
• expo-document-picker - [document-picker] created plugin #11977
• expo-apple-authentication - Created plugin for apple authentication #11979
• expo-firebase-core
• expo-google-sign-in this package should be deprecated instead
• expo-firebase-analytics

Additional Functionality

Not required for parity with the current managed workflow, but these should be mostly easy to add and crucial for having good payments/development support in Expo.

• expo-payments-stripe - [EMS] Create dev tooling for config plugins #11574
• expo-in-app-purchases
• expo-dev-menu
• expo-dev-launcher

Misc

• expo-local-authentication
• expo-screen-orientation