Re-sort module properties after merging

[HebaruSan]

Problem

After merging KSP-CKAN/NetKAN#9882, I noticed ksp_version was appearing out of its normal ordering:

Cause

The GitHub module has no versioning info at all, whereas the one from SpaceDock has a game version, and otherwise they're identical, so the merge code is appending just that one property from the SpaceDock module onto the GitHub module after it's sorted.

Changes

Now the merge logic reapplies sorting, so multi-host .ckans will have the same property ordering as single-host ones.