XD-1958 Fix Partitioned Batch Jobs

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

With the `RabbitMessageBus`, the `replyChanel` header was
not propagated and so the aggregator failed to deliver
the step execution results to the partition handler.

Use a `HeaderChannelRegistry` to propagate a key
referencing the `replyChannel`.

With the `RedisMessagebus` there was no provision to
propagate *any* headers needed for paritioning
(`correlationId`, `sequenceSize` etc).

Add a list of standard headers to propagate and a
facility to add additional headers (at the bus level).

Add tests to assert propagation; also tested manually
with the file->jdbc job with 3 partitions (both Rabbit
and Redis).
XD-1702 XD-1965 Re-adding spring-data-hadoop jars to classpath

- Looks like we removed too much, the UI REST endpoints depend on spring-data-hadoop-batch tasklets
XD-1970 Improve Thread Naming for Rabbit Bus

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

Previously, all listener container threads in the
RabbitMessageBus had the same name.

This made it difficult to debug.

Use the queue name as the thread prefix so that you
can easily identify the module in the log.
Fixed compile warnings
XD-1870 More Rabbit Host/Port -> Addresses

Some places were missed when changing the configuration
from host/port to addresses.

Also remove vcap from application.yml.
XD-1960 Fix ArrivingContainer deployment

- To avoid duplicate of modules into the arriving container,
use `ModuleDeploymentsPath` to check if the same module type of the given
stream is already deployed into the arriving container
- Fix for both stream/job module deployments

2nd commit message:

Fix code reivew comments

- Use module label instead of module type when detecting pre-existing deployment in
the container
- Refactoring changes
XD-1870 Allow Rabbit Modules to Inherit Properties

Set the default values of addresses, username, password,
vhost to the property names from application.yml/servers.yml.
XD-1510 Lower some logging levels

Fix o.s.i -> o.s.amqp

Remove noisy Spring Batch @Configuration warning

Using log4j for tomcat logs
XD-1976 Unable to deploy job in UI

* Add test case for `getModuleNameFromJobDefinition` when retrieving the module name for definitions without parameters
* Fix `getModuleNameFromJobDefinition`
* Disable the `Deploy` button as long as no module name has been retrieved
XD-1964 Suppress LoggingApplicationListener warning

- The issue with LoggingApplicationListener's incorrect warning
message is fixed in spring-boot but since we can't upgrade to
the latest, as a temporary fix setting the log level for
LoggingApplicationListener to `ERROR`
XD-1974 WebUI: Pull `Back` button to top right

- Fix the `Back` buttons for all the details pages
XD-1979: Restore 'log' sink output