Ensure that all plugins used by configs are listed as peer dependencies

[G-Rath]

We should be including all plugins used by our configs as peer dependencies, to make it easier to get a working config (since package managers will at least warn if a peer dependency version doesn't match our constraints).

Currently we're only listing required peer dependencies aka those that are used by the standard config, but we should also be listing the plugins used by our optional/extra configs using peerDependenciesMeta to mark the dependencies as optional.

We'll want to have a test that ensures all plugins used by each config is listed as a peer dependency, and that they're marked as optional or not as appropriate.

We will also need to update generate-configs-list to handle optional dependencies.

[github-actions]

🎉 This issue has been resolved in version 2.3.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀