Feature Request: an option to `paket install` that would ignore upper bound restrictions

It came while discussing restrictions in https://www.nuget.org/packages/FSharp.Control.Reactive#dependencies-body-tab and the fact there is new major version of the System.Reactive library, making the F# package conflicting with usage of it.

@TheAngryByrd suggested we could have some form of YOLO option that would ignore upper bound restrictions.

Thinking some more, I think it should apply to transitive dependencies, but the restrictions put in the paket.dependencies should still be honored, in terms of resolving the dependency.

Or maybe it should be involved only in case of unresovlable conflict.

It would be good to have sample paket.dependencies that highlight what is the current block about, and what we'd expect in .lock file, if the YOLO option was used.

Start by reviewing the current paket install dependency-resolution behavior and the referenced NuGet conflict. Use sample paket.dependencies inputs to define how transitive upper bounds differ from direct restrictions, then specify the expected .lock output for the proposed option. The issue is done when the option's behavior is unambiguous and covered by representative examples.