use fixed jar-dependencies gem - fixes #1942 + #1965
load resources from jruby-classloader
each required jar will be added to the LOAD_PATH removing the need to handle
those jar (and its ruby script content) explicitly with the JRubyClassloaderResource

each required jar will be add to LOAD_PATH using jar:file: protocol URIs. with
this all Dir glob, etc will work on those jars and its embedded ruby scripts.
putting the jruby-classloader as context classloader means that all attached "jars" can be found via
the Thread.currentThread.contextClassLoader which means all ruby scripts will be found through this pass.
running jruby from other environments like servlets just leave the context classloader as parent.

Dir-glob does not work in general with the Thread.currentThread.contextClassLoader and this would also
shadow the LoadPath entries for the attached jars since the context-classloader gets inspect first

finally it keeps the classloader semantic uniform wether executed from commandline or inside a j2ee container
or osgi framework
call generated test script differently then the any existing files, to avoid finding
it on the classpath and loadpath
run the load_path test only in 1.9 mode since 1.8 finds things on CWD
make sure we have "." in the LOAD_PATH for 1.9 mode
in some environments JRuby is not loaded via the context-classloader
use runtime.getCurrentDirectory to determine whether a ruby script comes from "."
do not test for working openssl on OSGIScriptingContainer
remove protocol and space when comparing and allow %20 for jar:file:-URIs
do load yaml ruby scripts from jruby.jar
give uri: protocol higher priority
add jars from JVM classpath to LOAD_PATH so that JarResource can use them
* add property/config to fallback to legacy loading via JRubyClassloader
* add property/config to switch back to legacy loading
* use uri:classloader: protocol for setting jruby.home
* give preference to RubyInstanceConfig.class.getClassLoader instead of Thread.currentThread.contextClassLoader
simplify IsolatedScriptingContainer and make sure URLResource uses the right classloader
do not run integration-test per default