Drop @expo/config-plugins dependency in favor of an expo peer dependency

[EvanBacon]

Why

We are having issues of users having conflicting versions of @expo/config-plugins, this isn't a huge issue with the Expo SDK since everything is versioned but it seems fine to just depend on the version of config-plugins that is in the SDK.

Test Plan

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 expo prebuild & EAS Build (eg: updated a module plugin).

[brentvatne]

this is great! i missed this pr yesterday and discussed the same thing in #sdk-release after you'd already opened this 😂

• should we do this for @expo/config and @expo/config-types as well?
• what do you think about re-exporting config-plugins and other config packages from the expo package in the same way that we do with metro-config?

[EvanBacon]

@brentvatne Probably fine for config types, config shouldn’t really be a big issue since it hardly ever changes.
I think maybe we should play the re-exports by ear and wait until we have a proper use case for them.

[brentvatne]

@EvanBacon - the concern is that @expo/config also depends on @expo/config-plugins

[KiwiKilian]

Should the dependency also be removed in community-driven plugins like @rnmapbox/maps?

[lehresman]

@EvanBacon - the concern is that @expo/config also depends on @expo/config-plugins

Any update on this? The dependency of @expo/config on @expo/config-plugins is biting me currently. I'm not able to upgrade config-plugins because of this. I keep getting this when expo doctor is run when building Android via EAS build:

Running "expo doctor"
- Finding all copies of expo-modules-autolinking
[stderr] [16:26:47] Expected package expo-modules-autolinking@~0.10.1
[stderr] [16:26:47] Found invalid:
[stderr] [16:26:47]   expo-modules-autolinking@0.8.1
[stderr] [16:26:47]   (for more info, run: npm why expo-modules-autolinking)
- Finding all copies of @expo/config-plugins
[stderr] [16:26:54] Expected package @expo/config-plugins@^5.0.0
[stderr] [16:26:54] Found invalid:
[stderr] [16:26:54]   @expo/config-plugins@4.1.5
[stderr]   @expo/config-plugins@4.1.5
[stderr]   @expo/config-plugins@4.1.5
[stderr]   @expo/config-plugins@4.1.5
[stderr] [16:26:54]   (for more info, run: npm why @expo/config-plugins)
- Finding all copies of @expo/prebuild-config
Command "expo doctor" failed.
bash exited with signal: SIGTERM

When I run npm why it shows that @expo/config-plugins@4.1.5 is required in @expo/config.

Is there a workaround for this?