Multi container testing module

Introduction of Spring XD multi container tests under the module:

  spring-xd-distributed-test

External JVM launch support provided by the Oracle Tools framework:

  https://java.net/projects/oracletools

Since these tests have the potential to add multiple minutes to the
build, they are not enabled by default. Include the following system
property command to include distributed test execution:

  -Drun_distributed_tests=true
XD-1899: IllegalStateException on single node shutdown

When the application context is shut down, the cache
will also be shut down (similar to DeploymentSupervisor).
XD-1703 Add admin and container memory settings
XD-1684 JBoss HornetQ Infrastructure (JMS Source)

JIRA: https://jira.spring.io/browse/XD-1684

Infrastructure files for JBoss HornetQ.

Note: Due to a gradle issue, we cannot automatically
pull in hornetq dependencies.
See http://issues.gradle.org//browse/GRADLE-3074
XD-1751 Connection Pool settings for jdbc modules

* Includes common pool settings as well as tomcat enhanced attributes
* Initial size is set to zero vs. the default of 10.
* Jdbc Unit has a test for testOnBorrow setting.
* hdfsjdbc, jdbchdfs & filejdbc testing will be covered by acceptance tests
* Code Polishing

Jdbc Connection pool settings now set via yml

Originally the PR used JDBCConnectionPoolMixin in order to set the connection pool settings.  However this proved to be a bit overwhelming for users when trying to setup a jdbchdfs, hdfsjdbc,filejdbc or filesink.
Now the pool setting will be setup via a servers.yml and application.yml

Connection test for shell was removed.

No longer valid, because settings will be established via the .yml files.

Conn Pool Config consolidated to one location in yaml

* Servers.yml
* application.yml

JdbcConnectionPool metadata is now available.

1) Add key datasource and pool variables in servers.yml
2) Add commented out section of datasource and pool variables in modules.yml as an easy way to customize the datasource used for modules but not for the XD infrastructure
3) For any modules that use jdbc functionality, add something like maxIdle = ${spring.datasource.maxIdle} into that module/job property file.
4) investigated to see if there was a way to inject a common snippet of connection pool xml into jdbc.xml, hdfsjdbc.xml, jdbchdfs.xml & filejdbc.  There was no smooth way to do this.

Jdbc Conn Pool autocomplete options are hidden.
XD-1869: Expose mapped(Request|Response)Headers

Also fixed missing bean factory in Redis Bus (grussell).
XD-1768 User should be able to specify deploy properties for Jobs

XD-1768 Code Review Changes

XD-1768 Polishing and Rebased with MASTER
XD-1768 User should be able to specify deploy properties for Jobs

XD-1768 Code Review Changes

XD-1768 Polishing and Rebased with MASTER

XD-1889 UI Needs to handle the finer-grained deployment statuses

* Add status column to definitions table
* Use the new statuses to disable/enable buttons
* Add popover illustrating and describing the statuses

Jira: https://jira.spring.io/browse/XD-1889

XD-1889 Polishing UI rendering

XD-1889 Code review - add statuses for streams

XD-1889 Fix deploy Stream functionality
XD-1889 Changes on merge

- Handle `incomplete` and `failed` state
  - enable `deployJob` action on these states
XD-1895 - Use Boot plugin and IO Platform for versions where possible

https://github.com/dsyer/spring-xd/commits/boot1.1.3

- Remove some versions that are provided by Boot plugin
- Move spring-boot plugin to java projects
- Fix bug in bootRepackage declaration
- Remove (unused) springBootVersion
- Fix formatting and remove versions that were added on master
Revert back to original build file

- Not sure why assert clause in testGetBatchJobExecutions needed to be changed. This was present in the original PR.
XD-1753 Job parameter default date format to 'yyyy-MM-dd'
XD-1858: Provide error location when tapping fails
XD-1914 Handle deploymentStatus for moduleCount zero

- If the module count for a module on a given stream is zero, then the stream is considered
deployed at least one module is deployed.