Fix: making Runway runnable from UberJAR (or any JVM classpath)

The local-git-version feature had caused a regression, making Runway only runnable from its own repo, and no longer from an UberJAR as documented. This is solved by enabling callers of Runway to supply the Runway version explicitly, via a runway_version JVM Property.

What's more, the documentation omitted the necessity for SSL-related JVM properties; this is now fixed.