Fixes #1945. File.exists?("broken_symlink") returns true. Fixes #1950. All RubyFileTest methods have a race condition
This test output does not match MRI any version.  Bad test
Remove lstat check until we find where this is needed
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
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
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.
ignore file: protocol if present
call generated 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
adjust Dir.entries to be uri-like
add "." to LOAD_PATH as some test need this
in some environments JRuby is not loaded via the context-classloader
use runtime.getCurrentDirectory to determine whether a ruby script comes from "."
just add "!" to jar entries of LOAD_PATH
do not test for working openssl on OSGIScriptingContainer
allow %20 for jar:file:-URIs
use runtime.getJRubyClassLoader.getParent for uri:classloader: protocol - a bit more generic as before
make sure we have "." in the LOAD_PATH for 1.9 mode
remove protocol and space when comparing