Fixed the userId changing issue [TACHYON-171]

The problem is that if a user opens a client connection and starts
writing a file, but finishes writing after a certain
timeout (user.master.client.timeout.ms), then the MasterClient will
close its connection before the file is written, then reconnect and get
a new userId, which will screw up the write.

I'm not quite sure why we automatically close the connection if it
hasn't been used for a while, as we aren't really wasting any resources
by keeping it open. This change removes the original heartbeat
mechanism, which tracks how recently the client has been used and closes
the connection automatically, with a heartbeat that pings the master to
check the connection, and closes the client only if it can't connect to
the master. Now on a long write (or any operation with the client that
takes longer than user.master.client.timeout.ms), we won't reconnect and
change the userId.
Documentation fixes
Undid the changes to MasterClient retry logic
Added javadoc/source jar in build so publish will include them
use closer to close resources in TachyonFile
Fixed formatting issues
Merge pull request #518 from shimingfei/TachyonFileFix

use closer to close resources in TachyonFile
Merge pull request #516 from dcapwell/sourceAndDocForBuild

Added javadoc/source jar in build so publish will include them
more documents
initial openstack integration

Signed-off-by: rootfs <hchen@redhat.com>
Merge pull request #477 from manugoyal/userid-changing-fix

Fixed the userId changing issue [TACHYON-171]
Merge pull request #520 from rootfs/wip-openstack

[Tachyon-191] deploy tachyon cluster on openstack