Sort GUI KSP version column correctly

[HebaruSan]

Problem

If you sort by Max KSP version, 1.10 comes between 1.1 and 1.2, which is wrong.

Cause

Currently this column sorts as a string, which only works if the lexicographical sort order of the strings corresponds to the true sorting of the versions, which it doesn't.

Changes

This gets a bit tricky. We need to expose the GUIMod's KspVersion object, but we can't just sort by that object naïvely, because KspVersion.CompareTo sorts undefined values inappropriately for upper bounds; it considers 1.8 < 1.8.0, and any < everything. We want the opposite, so we can't use .OrderBy or .OrderByDescending for this.

Instead, ManageMods now has an alternate Sort overload that takes a Comparison<DataGridViewRow>, which can handle comparisons between two objects rather than just returning a sort key for one object. The KSP version column uses this Sort with a new function that treats undefined components of KspVersion as maximum rather than minimum. This causes the column to sort according to actual compatibility.

Fixes #3105.

Quirks

Note that this logic makes finer distinctions in mod compatibility than the .ToYalovString() display function does. This means that the alphabetical fallback sorting may sometimes appear to reset unexpectedly. For example, consider this block of mods that all display as "1.10.9":

The Versions tab reveals:

• SmokeScreen is compatible up to 1.10.90
• AblativeAirbrake through Tundra Technologies are compatible up to 1.10.99
• Astrogator is compatible up to 1.10

So while the column's strings are superficially the same, the introduction of a KSP 1.10.95 or KSP 1.10.100 would draw out real distinctions in their compatibility, which this sort order reflects.

[DasSkelett]

Version comparison is always fun!