Allow documentation/checking of dependencies via ksp-avc file

[jrossignol]

For CKAN files, it is possible to document dependencies for a mod. You can document the names and minimum versions of required mods. Right now, this information needs to be maintained in the NETKAN or CKAN files, which is a bit of a pain - it would be nice if this information could be pulled from the ksp-avc files.

Which brings me to my request. Can we enhance KSP-AVC to support documenting and checking dependencies for a mod? I would want:

• Ability to list mods in the .version as a dependency, as well as the minimum version that is required
• Ability to list a mod, but flag as disabled for checking (as some mods may not have .version files, but this information would still be useful in the CKAN/NetKAN system).
• Ability to have KSP-AVC check for version incompatibilities and report to the user
  • Stretch here would be to support checking the assembly version info for non-AVC mods (for ones that actually provide this).

The argument against this change of course is that if all the mods in question are using .version files, this type of check should be unnecessary - since the user would already be notified of mods that are out of date. But the information would still be useful to get into CKAN. (Note that I'm not affiliated with the CKAN project in any way. So getting them to read the information from the .version file would be the next hurdle).