Peer Dependency Conflict on @awesome-cordova-plugins/core between v5 and v6 plugins

[eyedean]

Greetings,

My Issue

I am trying to install two different versions of the same plugins (we really need to support the old one, too), but they conflict over the @awesome-cordova-plugins/core version.

The General Issue

My understanding is that having @core as a peer dependency of all plugins with a fixed major version means that ALL the plugins must use the same core version. So, if you have one plugin upgraded to v6, then you MUST upgrade ALL plugins to v6. If that's the case, it would be very limiting.

What would you recommend if someone wants to use some v5 and some v6 plugins during the transition periods? (By the way, I am on NPM.)

My Findings

1. From this issue, I found that @danielsogl updated the MIN_CORE_VERSION in /scripts/tasks/publish.ts from 5 to 6. I am wondering if it could be ^5.1.0 || ^6.0.1 if it's not breaking anything.
2. Going through the CHANGELOG for 6.0.0., I found that the update is "Features: core: use angular ivy." We are not using angular or ivy. So, would it be fine to use v6 core for v5 plugins or v5 core for v6 plugins? (If so, I can fork the repo and change it unblock myself)

Any advice will help a lot! Thank you so much for your attention and participation. :)