Handle incompatible force-installed dependencies of recommendations

[HebaruSan]

Problem

1. Find an incompatible mod that has a compatible recommendation or suggestion that depends back on the original mod.
   (One example is RasterPropMonitor and RasterPropMonitor-Core, which are not compatible with KSP 1.11, and recommend ASETProps, which depends on RasterPropMonitor-Core.)
2. Use the Versions tab checkboxes to add the incompatible mod(s) to the change set.
3. Click Apply to go to the recommendations/suggestions screen
4. Check the checkbox for the mod that depends on the incompatible mods you're force-installing.
   (In our example, this is ASETProps)
5. On Windows:
   
   On Linux, the same exception is printed to stdout.

   CKAN.DependencyNotSatisfiedKraken: ASETProps dependency on RasterPropMonitor-Core 1:v0.30.2 or later version (any) not satisfied
      at CKAN.RelationshipResolver.ResolveStanza(IEnumerable`1 stanza, SelectionReason reason, RelationshipResolverOptions options, Boolean soft_resolve, IEnumerable`1 old_stanza)
      at CKAN.RelationshipResolver.Resolve(CkanModule module, RelationshipResolverOptions options, IEnumerable`1 old_stanza)
      at CKAN.RelationshipResolver.AddModulesToInstall(IEnumerable`1 modules)
      at CKAN.ChooseRecommendedMods.FindConflicts()
      at CKAN.ChooseRecommendedMods.MarkConflicts()
      at CKAN.ChooseRecommendedMods.RecommendedModsListView_ItemChecked(Object sender, ItemCheckedEventArgs e)
      at System.Windows.Forms.ListView.OnItemChecked(ItemCheckedEventArgs e)
      at System.Windows.Forms.ListView.WmReflectNotify(Message& m)
      at System.Windows.Forms.ListView.WndProc(Message& m)
      at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   

Cause

The conflict checker in the recommendations/suggestions screen doesn't know about the mods we're force-installing, so when it asks the RelationshipResolver to look for conflicts, it finds out that the dependencies aren't satisfied.

Changes

• Now LoadRecommendations has parameters for the mods that are planned to install and remove, and it includes them in the mods it passes to the RelationshipResolver for checking conflicts
• If we somehow get this exception again anyway, we now catch it and display it instead of letting it go to the unhandled exception handler:
  

Fixes #3303.

[HebaruSan]

@Arkhorse, there's a test build available if you scroll all the way down to the bottom of this page:

• https://github.com/KSP-CKAN/CKAN/actions/runs/597027887

[DasSkelett]

Ah, and it didn't know about the mods selected via the normal modlist checkbox either, but that wasn't a problem because the resolver could just find a compatible version to satisfy the dependency. 💡

[DasSkelett]

The exception was only visible in the terminal, that explains a lot...

Looks good, thanks.