Fix NetKAN staging

[HebaruSan]

Background

The NetKAN bot has a "staging" option that is intended to allow for manual review of bot updates before they go into CKAN-meta. If you put this in your .netkan:

    "x_netkan_staging": true,

... then the bot will put your mod's updates in a separate branch and submit a pull request on GitHub, which can then have the validation scripts run and be merged by metadata maintainers if it looks OK.

The following modules currently have metadata set up to use this feature:

• ContractConfigurator-HistoricMissions
• ContractConfigurator-HistoricMissionsRSS
• FerramAerospaceResearch
• Kopernicus
• KSPInterstellarExtended
• MilitaryVehicleChassis
• PlanetWiki-OPM
• RoverFuelTanks
• RoverWheelSounds
• SovietConversion
• StockVisualEnhancements
• SVE-HighResolution
• SVE-LowResolution
• SVE-MediumResolution

Problem

Currently the metadata does not trigger the feature. Those mods are not going through a staging procedure when they update.

Cause

The property name is wrong in the Perl code; the hyphens should be underscores:

NetKAN-bot/lib/App/KSP_CKAN/Metadata/NetKAN.pm

Lines 102 to 104 in 3a659d7

	method _build_staging {
	return $self->_raw->{config}{'x-netkan-staging'} ? $self->_raw->{config}{'x-netkan-staging'} : 0 ;
	}

So the feature is implemented and live, but it's not being used.

Changes

Now the correct property name is used. This will enable staging.

(Also fixed spelling of "commited" in a few message strings.)

Fixes #60.

[coveralls]

Coverage remained the same at 91.677% when pulling 714e546 on fix/staging into 3a659d7 on master.

[techman83]

Tests pass now (dependency was briefly having an issue on 5.20).

Thanks for updating this!

[politas]

I was wondering why nothing seemed to come through the staging process.