KSP2 netkan validation

[HebaruSan]

Motivation

As we advance toward the finish line of KSP2 support, we are getting closer to the point where we will need to be able to validate, review, and merge KSP2-NetKAN pull requests. This will require updating xKAN-meta_testing to support the new game.

Problem

Only KSP1 support exists for:

• Retrieving known game versions from GitHub
• Creating a dummy game instance
• Inflating .netkans
• Validating .ckans

Changes

Now the Action has a game parameter, defaulting to KSP, which allows the configuration file to specify how to get game versions and the value of the --game parameter for netkan.exe and ckan instance fake commands. This is done by creating a new Game abstract base class with derived classes Ksp1 and Ksp2, which provide public properties specifying their short names and their known game versions. Code that needs these values is updated to get them from Game objects that are now deduced from the GAME environment variable and then passed around.

In the process of making these changes, the validator is now switched from retrieving the embedded build map, which has been renamed to builds-ksp.json in KSP-CKAN/CKAN#3797, to using the remote build maps, which are not subject to naming collisions because they're in separate repos.

• Note that Multi-game fakery CKAN#3811 must be merged first for the --game parameter to be available everywhere it's needed!

[HebaruSan]

Let's see if this works...

[techman83]

All looks pretty reasonable 🙂