Ensure that tipsy hovers remain active after a job refresh
Jobs are automatically being refreshed from the server. This
fix ensures that the tipsy hovers associated with them are
refreshed as well.

See:
https://jira.springsource.org/browse/XD-837

Also,
*make sure that job instances returned with simple job name
*simple popup for specifying launch parameters in UI.
XD-813 Update BatchJobLocator on XD job removal
- When XD job is destroyed, the job name entry is removed from
  BatchJobLocator so that the Batch admin's launchable flag is set to false.
- Keep the 'isJobParameterIncrementable' flag in a separate table
  JOB_REGISTRY_INCREMENTABLES
  - Handle insert/update on subsequent job creation with same name
- Fixed BatchExecutionController's REST endpoints & jobName handling
- Moved HSQLServerBean, Batch support classes  & registry schema sql
  out of dirt.plugins.job package
- Fixed tests to use test specific hsqldb properties when loading batch.xml

- Upgrade hsqldb version to 2.3.0 and exclude it from
  spring-batch-admin & spring-data-hadoop projects

- Moved REST endpoint 'batch/executions/{jobName}'
  to 'batch/jobs/{jobName}/executions'