XD-745 & XD-745 Use Spring batch admin
- Added spring batch admin manager dependency (1.3.0.BUILD-SNAPSHOT)
- Added BatchJobController & BatchJobExecutionController
 - Currently these controllers have list JobInfo/JobExecutionInfo
 - Map the requests to '/batch' to avoid conflicts with existing
   XD JobController
 - Created BatchJobLocator that extends ListableJobLocator
  - This will store job name & isIncrementable value for the job
 - Added DistributedJobService that extends batch SimpleJobService
   with unsupported methods that depend on runtime Job instance query
   from JobLocator
- Started HSQLDB in server mode
 - This will enable accessing the schema outside the JVM it is running
 - Removed the global bean config batch.xml and created batch config
   for AdminServer & ContainerLauncher
 - Added hsqldb.properties in config to set hsqldb related properties

XD-744 Fix review comments
- Added Profile based config to load batch config beans
- Added /batch/jobs/executions/{jobName} rest end point
- Fixed the type level RequestMapping to read 'batch/jobs'

XD-744 Updates to batch admin controllers
 - Added REST endpoints to GET jobExecutions & jobs by jobName
 - Added tests for BatchJobsController & BatchJobExecutionsController
Update UI to use the new batch admin api

- Enable the details request mapping
  Also, remove the '.job' suffix of job names when sending
- job info across the http request.
- update gitignore for sublime metadata files
- Change rest endpoint path
- Ability to display job instances
Fix BatchJobsControllerIntegrationTests
- Fix the jobName to have ".job" suffix as per the controller changes
XD-685 Add Plugin beforeShutdown callback

Allow Plugins to perform module cleanup using
Spring beans from the Module's context
XD-685 Support tap namespace in named channels
XD-685 Add bridge cleanup methods to ChannelRegistrySupport
XD-685 Add create/delete pub/sub channels to ChannelRegistry, disable tap method
XD-685 Create tap pub/sub channels on stream creation

- Create channel "tap:streamname.modulename" for each
module in a new stream, tapping into the module's output
channel. These tap channels can later
be used as named channels in other stream definitions.

- Supported syntax for tapping is now "stream create
mytap --definition ":tap:streamname > sink" or
":tap:streamname.module > sink". "tap:streamname"
will not work on a stream where source module is
a named channel (for now)

- Temporarily disallows tapping of named channels,
labels, or streams whose source is a named channel
XD-685 Remove support for tap commands