XD-1581 Fix config location in scripts

- Set config locations prefix file:

  - Fix non-batch script files

- Fix scripts for config location

  - Always append "/" to XD_CONFIG_LOCATION so that when it gets appended for
XD_MODULE_CONFIG_LOCATION it is valid
  - Also, having "//" (if the existing property already has "/" this change would still add one)
on both *nix and windows seem to work fine.

- Fix xd.config.home to use XD_CONFIG_LOCATION

  - Fix the scripts that use XD_CONFIG_LOCATION
Updated README for M6
Add lengthFieldLength parameter to options and config classes
Install redis - slackware platform update

- Support for Slackware 32 & 64 bit to install-redis script
XD-1582 ignore if no metadata node yet
Support spring resource URL

- Remove explicit file: prefix for XD_CONFIG_LOCATION and
XD_MODULE_CONFIG_LOCATION
Release version 1.0.0.M6
Increment version to 1.0.0.BUILD-SNAPSHOT
XD-1580: Undeploy modules when ZK disconnects

In method registerWithZooKeeper, the module deployments cache is
started before saving the container attributes. This way if there
is an exception thrown while saving the attributes, the deployments
cache is not affected.

At some point we may want to consider trapping exceptions from
this method, or perhaps even shutting down the ZK connection if
an exception occurs. I was seeing a NodeExists exception for
the ephemeral node created by this method, but that exception
seems to have gone away with the other changes in this commit.

In method onDisconnect the modules are now undeployed when the
connection to ZK is lost. This is desirable because the admin
leader will try to redeploy those modules on another container.

In StreamModuleWatcher and JobModuleWatcher, instead of blindly
setting the watch on every non-delete event, the watch is only
set if the connection to ZK is established. This change seems
to prevent the exception described above in registerWithZooKeeper
although I don't understand how they are related.