Extend -single-instance fix to 1.9

[DasSkelett]

Problem

#2902, which was fixed for KSP 1.8 in #2931, still applies to KSP 1.9 unfortunately:

Set current directory to /HDD/KubuntuSteamGames/steamapps/common/Kerbal Space Program
Found path: /HDD/KubuntuSteamGames/steamapps/common/Kerbal Space Program/KSP.x86_64
Speicherzugriffsfehler (Speicherabzug geschrieben)

(Now you know the German translation for a segmentation fault)

Changes

The version range for which we remove the -single-instance command has been extended to include 1.9.

I created a new helper function which allows to create a KspVersionRange from two KspVersion objects. The resulting version range extends from the lowest possible version of the first argument to the highest possible version of the second argument.
It uses the KspVersion->KspVersionRange logic from kspversion.ToVersionRange().

[DasSkelett]

Thanks for the suggestions!
I also added a test, while this might be implicitly tested in tests for the StrictGameComparator, explicit ones are a good idea.
(Without the test this PR reduces the code size :P)

[HebaruSan]

Nice! Want to try merging your own changes to master?

[DasSkelett]

No risk no fun 😁

[HebaruSan]

@DasSkelett we need this for 1.10,

https://forum.kerbalspaceprogram.com/index.php?/topic/154922-ckan-the-comprehensive-kerbal-archive-network-v1280-dyson/&do=findComment&comment=3835778

[DasSkelett]

Oh, thanks! Also: System.ComponentModel.Win32Exception (0x80004005): Cannot find the specified file 🙄

And xdg-open doesn't want to open binaries, so Utilities.ProcessStartURL is out:

Bei der Datei file:///NAS/games/KubuntuGames/steamapps/common/Kerbal Space Program/./KSP.x86_64 handelt es sich um ein ausführbares Programm. Es wird aus Sicherheitsgründen nicht gestartet.

Rough translation:

The file "file:///NAS/games/KubuntuGames/steamapps/common/Kerbal Space Program/./KSP.x86_64" is an executable program. It won't be started for security reasons.

We'll have to find yet another workaround for this...

[DasSkelett]

Well, this is weird. I don't know how I got the Win23Exception to show up earlier, but it's not happening anymore.
So we should be fine just extending the fix.