Unmet Peer Dependency Warnings

Description

Whenever the yarn command is used to install dependencies for projects consisting of packages from the config repo, an array of warnings are seen, most of which are Unmet Peer Dependency Warning.
As per my understanding, this behavior is the result of the mismatch of peer-dependencies mentioned in the official babel packages and the versions that we have used inside our packages under the config repo.
For example:
medly/babel-config-react has @babel/plugin-transform-react-jsx and medly/babel-config (configs/packages/babel-config) in their dependencies. When we look into the package.json of babel-config, we have "@babel/core": "^7.14.5" as one of its dependencies. However, @babel/plugin-transform-react-jsx has a peer dependency of "@babel/core": "^7.0.0-0".
This dependency conflict might be the cause of the warnings.

To Reproduce

Steps to reproduce the behavior:

1. Clone the Satellite Repo
2. In the terminal, use the following command: yarn

Expected behavior

No warnings should be given for config-related packages.

Screenshots

Run yarn in the Satellite Repo to reproduce the warnings, then compare the dependency declarations in packages/babel-config-react/package.json and packages/babel-config/package.json with the referenced Babel package metadata. Done means installing the config-related packages without unmet peer dependency warnings.