FR: Allow users to override dependancy version requirements

[EatThePath]

I was going to refer to this in commentary on #194 because I thought I'd already filed this, but turns out no

When a mod's dependencies are somehow broken or invalid, my ideal situation is that Knossos would have a way to say "Here are the best version matches I could come up with, and here's the requirements they don't match, no guarnetees it'll work but you can launch if you really want to." and a variant of that interface that would let the user say "I know the mod says launch with MPVs 3.2.x but lets try 3.3.x just to see."

Yes, editing the mod.json files lets you do some of that, but it's not the most user friendly way to go about it. Having something built into the launching interface would also smooth over the tension between mods needing to be strict about versioning for stability and needing to be lax about versioning to take advantage of new stuff even if the maintainer drifts out of the community.