chore: add constraint for duplicate dependency declarations

[merceyz]

Q	A
Tests Added + Pass?	Yes
License	MIT

Added a constraint to enforce the change in #13737, while it doesn't cause issues in published packages since devDependencies are ignored, it can cause an issue in the monorepo since devDependencies wins when a dependency is declared in both dependencies and devDependencies.

[babel-bot]

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/48615/

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 251abb8:

Sandbox	Source
babel-repl-custom-plugin	Configuration
babel-plugin-multi-config	Configuration

[JLHwung]

We can apply the constraints to (peerDependencies, dependencies) too.

[merceyz]

@JLHwung That's actually a valid pattern, Yarn will use the peerDependencies if provided by the parent and dependencies if not, "peer dependencies with a default" if you will.
https://yarnpkg.com/configuration/manifest/#peerDependencies