Dependency Warnings

While PowerShell allows to you install multiple versions of a module side-by-side, if that module contains conflicting assemblies, we may want to warn that assembing binding redirect will occur and instruct the user the order in which to load their modules if they choose to use them simultaneously. This will be output as a warning. We only want to do this if the module is a binary module (how to detect) and two versions are found to have incompatible ranges (e.g. one requires maximum of 3.0 and another is unbounded and there is a 4.0 release out.

The issue does not name files, tests, or an entry point. Start by locating dependency handling for binary PowerShell modules and assembly binding redirects, then determine how incompatible version ranges are detected. Done means a warning explains the conflict and module load order when the affected modules are used together.

Written by the indexing model from the issue text.