Ignore invalid version ranges in the v3 feed

[scottbommarito]

Related to NuGet/NuGetGallery#3482

Currently, if the client tries to install a packages from the v3 feed with a dependency containing an invalid version range, it will fail. This is inconsistent with the behavior for v2, which is to simply install the oldest package. Because deleting old, broken packages from the gallery would upset users, and because we cannot guarantee that all feeds following the v3 protocol will implement it perfectly, we should abide by our v2 behavior and warn the user that the package has an issue but install the package anyway.

[ghost]

Due to lack of recent activity, this issue has been marked as a candidate for icebox cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will add a Triage:NeedsTriageDiscussion label and lead to a triaging process.
This process is part of the experimental Stale icebox issues cleanup we are currently trialing. Please share any feedback you might have in the linked issue.

[ghost]

This issue will now be closed since it had been marked Icebox cleanup candidate, but received no further activity in the past 14 days.