Paket should detect an unsolvable conflict sooner

Given a dependency file that contains FSharp.Core pinned to 4.0.0.1 and LiteDB.FSharp (which needs 4.2.3), Paket keeps looking to find a resolution by checking all other packages in the dependencies file e.g. FAKE, Argu etc. etc. - when in reality the resolution can never work because of these incompatible packages

• Dependencies file requested package FSharp.Core: 4.0.0.1
• LiteDB.FSharp 0.1.0 requested package FSharp.Core: >= 4.2.3

e.g. in the output, I see:

The process is taking longer than expected.
Paket may still find a valid resolution, but this might take a while.
 - FAKE 5.1.0
 - FAKE 5.0.0
 - FAKE 4.64.13
 - FAKE 4.64.12
 - FAKE 4.64.11
 - FAKE 4.64.10
 - FAKE 4.64.9
 - FAKE 4.64.6
 - FAKE 4.64.5
 - FAKE 4.64.4
 - FAKE 4.64.3
 - FAKE 4.64.2
 - FAKE 4.64.1
     FAKE 4.64.1 was unlisted
 - FAKE 4.63.2
 - FAKE 4.63.1
 - FAKE 4.63.0
 - FAKE 4.62.6
 - FAKE 4.62.5
 - FAKE 4.62.4
 - FAKE 4.62.3
 - FAKE 4.62.2
 - FAKE 4.62.1
 - FAKE 4.62.0
 - FAKE 4.61.3
 - FAKE 4.61.2
 - FAKE 4.61.1
 - FAKE 4.61.0
 - FAKE 4.60.0
  Conflict detected:
   - Dependencies file requested package FSharp.Core: 4.0.0.1
   - LiteDB.FSharp 0.1.0 requested package FSharp.Core: >= 4.2.3
   - Argu 5.1.0 requested package FSharp.Core: >= 4.0.0.1

It goes all the way back in time through every version of FAKE on nuget to "prove" that the resolution can't work.

Start by reproducing the dependency file containing FSharp.Core 4.0.0.1 and LiteDB.FSharp 0.1.0, then trace Paket's dependency-resolution path that evaluates FAKE versions. Done means the incompatible FSharp.Core constraints are reported without searching every unrelated FAKE version.