Fix SPARK-698. From ExecutorRunner, launch java directly instead via the run scripts.
Incorporate feedback from mateiz:
- we do not need getEnvOrEmpty
- Instead of saving SPARK_NONDAEMON_JAVA_OPTS, it would be better to modify the scripts to use a different variable name for the JAVA_OPTS they do eventually use
Merge remote-tracking branch 'cgrothaus/SPARK-698'

Conflicts:
	run
Fixed deprecated use of expect in SizeEstimatorSuite
Some fixes to the launch-java-directly change:

- Split SPARK_JAVA_OPTS into multiple command-line arguments if it
  contains spaces; this splitting follows quoting rules in bash
- Add the Scala JARs to the classpath if they're not in the CLASSPATH
  variable because the ExecutorRunner is launched with "scala" (this can
  happen when using local-cluster URLs in spark-shell)
Fix computation of classpath when we launch java directly

The previous version assumed that a CLASSPATH environment variable was
set by the "run" script when launching the process that starts the
ExecutorRunner, but unfortunately this is not true in tests. Instead, we
factor the classpath calculation into an extenral script and call that.

NOTE: This includes a Windows version but hasn't yet been tested there.
Added a local-cluster mode test to ReplSuite
Formatting
Refactored tests to share SparkContexts in some of them

Creating these seems to take a while and clutters the output with Akka
stuff, so it would be nice to share them.
Don't use forward slash in exclusion for JAR signature files
Be cute with Option and getenv.
Wrap lines.
Merge pull request #663 from stephenh/option_and_getenv

Be cute with Option and getenv.
Fixes to compute-classpath on Windows
Simplify Python docs a little to do substring search
Removing incorrect test statement
Look at JAVA_HOME before PATH to determine Java executable
Merge pull request #664 from pwendell/test-fix

Removing incorrect test statement