Local hadoop install support in tachyon startup scripts

Changes:
* Updated tachyon shell scripts to use dynamically generated TACHYON_CLASSPATH
* Added optional HADOOP_HOME to point to a local hadoop installation.
* Generate Tachyon + Hadoop in TACHYON_CLASSPATH if HADOOP_HOME is defined

These changes allow tachyon to share libraries (specifically UnderFileSystem) with the local Hadoop installation without duplicate JARs or conflicts with the packaged hadoop libraries.  Will also allow use of same/shared Hadoop configuration and eventual refactor/removal of any packaged Hadoop dependencies in build.

This simplifies hadoop configuration and library/JAR duplication.  Changes do not impact current behavior, user must uncomment/set the HADOOP_HOME in tachyon-env.sh first.

Somewhat unrelated fix:
* Updated the default JAVA path in linux to the generic symbolic link (will support most JREs without additional config)

Most distros will put the `hadoop` command in something like `/usr/bin/hadoop` so it will be in the path for most commands.  the `hadoop classpath` outputs the classpath that hadoop uses:

```bash
bash-4.1# hadoop classpath
/etc/gphd/hadoop/conf:/usr/lib/gphd/hadoop/lib/*:/usr/lib/gphd/hadoop/.//*:/usr/lib/gphd/hadoop-hdfs/./:/usr/lib/gphd/hadoop-hdfs/lib/*:/usr/lib/gphd/hadoop-hdfs/.//*:/usr/lib/gphd/hadoop-yarn/lib/*:/usr/lib/gphd/hadoop-yarn/.//*:/usr/lib/gphd/hadoop-mapreduce/lib/*:/usr/lib/gphd/hadoop-mapreduce/.//*
```

This command exists in both 1.x and 2.x, so its the most portable way to get hadoop jars (works with RPMs and tars).