Use XD job name for JobExecutionInfoResource

- The jobName of JobExecutionInfoResource should not have
  the default ".job" suffix we have for all the XD batch jobs.
  It is fine to have this jobName as is in JobExecutionInfo.
  Since the REST client domain resource should expose the
  actual job name we need to remove the ".job" suffix from it.
- Fixed the tests.
Make scripts more ubuntu-friendly

Following Janne's suggestions.
Also use echo "-e" to interpret newlines in messages.
XD-1012 Add user configurable batch JDBC settings

* Add feature where HSQLDB will not start if HSQL is not chosen for batch store
* Update the tests to support the hsqldb profile
* Update application template with rabbit settings.
* Update application.yml to support redis & Rabbit
* Update build.gradle to copy application.yml to the config directory as a template
* Remove redis.properties and rabbit.properties. These have been replaced by the settings in application.yml
* Admin will init job db if not already present
* Clean up batch.xml.
  * Removed default profile
  * Moved all adminServer database nested profiles to a single adminServer profile.
* Provide documentation

Jira: https://jira.springsource.org/browse/XD-1012
XD-1132 Support Topics in JMS Source

 Rename 'queue' property to 'destination'
 Add four new properties (default):
- pubSub (false)
- durableSubscription (false)
- subscriptionName (null)
- clientId (null)

Update the AmqBrokerAndTest test class to support sending to
topics.

Update `Sources` page on Wiki.
XD-1032 First stage for converting Hadoop module to isolated classloader scheme

- changing spring-data-hadoop version to 2.0.0.BUILD-SNAPSHOT so we can include
   the new spring-data-hadoop-store sub-project

- removing spring-xd-extension-hdfs replacing with spring-data-hadoop-store

- this is the first step in converting the spring-xd-hadoop module to remove hadoop
  dependencies from the spring-xd-dirt classpath and instead using isolated classloader
  scheme for any hadoop modules
XD-1044

Refactor module dependency tracking to be closer to stream deployment

Update tests so that logic for deleting a composite module in the ModulesController is covered

Move dependency mgmt of stream modules to the repository vs. the deployer

*  RedisModuleDefinitionRepository now stores all fields except, Resource, Classpath and ModuleOptionsMetadata in JSON form using Jackson.
*  Start to encapsulate functionality currently in ModulesController for working with composite modules into a new class - CompositeModuleDefinitionService.  In some ways analogous to the role Deployer's play with Stream/Job controllers.
*  Fix  RedisJobDefinitionRepository and RedisStreamDefinitionRepository serialization to JSON by using ModuleDefinitionMixin
*  Made changes to ModuleDefinition to more easily serialize to JSON.  This is actually a step backwards from the OO point of view.
*  Put duplicated code for module dependency management in RedisStreamDefinitionRepository and InMemoryStreamDefinitionRepository into a separate util class - no inheritance between the two repositories.

Merge ModuleDependencyTracker functionality into repositories
polishing
Fix execution list jobname at UI

- Use ExecutionInfoResource's jobName as is
XD-1125: First batch of properties file + short type names

Add options metadata for syslog modules

Add options metadata for tcp source

Change wording for input/outputType

Addressed review comments
XD Log settings updated to work with boot.

Scripts did not contain the xd.home parameter so logs failed.
Boot requires xd.logging to identify log config files. Scripts were set to use xd.logger.
Update configurations to reasonable defaults.

Updated .bat files replacing $ with % for env vars
Gemfire server enhancements