Fix max version column for wildcard compat

[HebaruSan]

Problem

Before KSP-CKAN/NetKAN#10149, StockWaterfallEffects's latest version was compatible with all of 1.11–1.12, but the max compat game version column showed 1.12.2.

Cause

AvailableModule.LatestCompatibleGameVersion tries to avoid checking compatibility of every single version of every mod against every known game version by quitting early if any of them are marked as compatible with all game versions:

CKAN/Core/Repositories/AvailableModule.cs

Lines 196 to 218 in a37eca5

	public GameVersion LatestCompatibleGameVersion(List<GameVersion> realVersions)
	{
	// Cheat slightly for performance:
	// Find the CkanModule with the highest ksp_version_max,
	// then get the real latest compatible of just that one mod
	GameVersion best = null;
	CkanModule bestMod = null;
	foreach (var mod in module_version.Values)
	{
	var v = mod.LatestCompatibleGameVersion();
	if (v.IsAny)
	{
	// Can't get later than Any, so stop
	return mod.LatestCompatibleRealGameVersion(realVersions);
	}
	else if (best == null || best < v)
	{
	best = v;
	bestMod = mod;
	}
	}
	return bestMod.LatestCompatibleRealGameVersion(realVersions);
	}

As it loops through that list, it tries to remember the highest max bound and then uses it at the end to get the compatibility. Unfortunately, the best < v comparison of two GameVersions can give wrong answers because GameVersion.Undefined is -1, which makes unbounded versions always compare as less than bounded ones, despite being able to match later versions. This makes 1.12.2 compare as greater than 1.12, so it's not a good idea to directly compare mixed bounded and unbounded game versions.

Changes

Now that comparison logic is performed by GameVersionBound.Highest, which properly handles comparisons with unbounded values.

Fixes #4141.