Allow for fulfilling peerDependencies from other dependencies

[yhnavein]

Feature.

What is the current behavior?
Let's assume following dependency structure:

- app
  - package1
    - [peerDep] packageA@1.0.0
  - package2
    - [dep] packageA@1.0.0

Currently if you try to install dependencies of the app then you will see a warning in the console about missing peer dependencies:

warning " > package1" has unmet peer dependency "packageA@1.0.0".

Warning is visible because yarn resolver tries apparently to determine peerDeps by looking at direct dependencies of the app. Is it possible then to add an option to extend this verification to include also further dependencies in the dependency tree?
An option through .yarnrc it would be the best

What is the expected behavior?

My expectation is to not see the above warning in my situation, as the dependency is fulfilled, but not directly under app.

Fixing it by adding packageA@1.0.0 directly to the app dependencies is not an option that is satisfactory for me.

Please mention your node.js, yarn and operating system version.

λ node -v
v10.14.2

λ yarn -v
1.17.3

Windows 10, but every platform works the same as far as I know.