XD-1547: Clean old entries in deployments/modules

The admin leader is responsible for removing containers in
/xd/deployments/modules. However if a container shuts down
without an admin leader running, the entries are not
cleaned up.

This change in the admin leader will cause it to clean up
old entries immediately upon its election.
Runtime modules cmd - minor fixes

- Rename "Properties" column to "Options"
- Filter out options with empty values
Fix ExpressionOrScriptMixin

- Fix the assertion to check for mutually exclusive options for expression and script
- Add transform processor tests using script and expression
Fix ProcessorsTests

- Move `transform-to-lowercase` groovy script into spring-xd-shell
- Update the script option in test case
XD-1378: Add options for router. Add IT test
XD-1378 Router sink test using script

- Also, moved the groovy script location to a package
Misc shell test cleanup

- testDestroyTap() leaves the file source input directory behind, use http source instead.
- use generateStreamName() instead of hard coded names
polish
XD-1550 Propagate BeanFactory to Hand-Built Beans

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

SI Components need access to a BF to get the message builder
factory.

Use mocks where needed for test cases.

Ran with SI 4.0.0.BUILD-SNAPSHOT with environment variable:

	SI_FATAL_WHEN_NO_BEANFACTORY=true

which forces a hard failure instead of just a log message.
XD-1552 disabled --transport for ContainerServerApplication
removed STORE from application.yml
XD-1378: Rabbit modules options

Remove PPC, move defaults to the metadata class, add test
XD-1378 Add RabbitMQ queue cleanup

- Cleanup queues after test
Remove schedule button from deployments page

- Schedule option is not yet implemented in the UI, hence removing it.
This was missed when XD-1436 was addressed.
fixed typo
fixed test dependent upon typo
XD-1539 revisited

The catch block on line 596 of ContainerRegistrar only included KeeperException,
but an IllegalStateException is thrown in the case where the CuratorFramework is
not in a STARTED state, and the checkExists() method is called.

For now, I've widened the catch block to Exception itself.
Enable jolokia only if JMX is enabled

- Make `endpoints.jolokia.enabled` use XD_JMX_ENABLED flag so that
JolokiaAutoConfiguration is disabled if XD_JMX_ENABLED is set to false
XD-1558 - Update to use spring shell snapshot to help test fix for SHL-133