XD-1499: Change config file name to server.yml
XD-1412: Fix profile activation for composed modules
XD-1378: options for splitter and transform
XD-1378: Refactor MQTT module options
Remove pmml-analytic from main tree
Rename analytics-pmml -> analytic-pmml
ModuleMetadata repo exclude redundant props

  - On find, Filter out default module properties like 'xd.stream.name' and 'xd.module.index'
  - those are readily available in the ModuleMetadata ID

Move ContainerArributes bean

- Move into ContainerServerApplication as it is relevant only to container
- was previously in ParentConfiguration

Handle empty module metadata
add toString to ContainerAttributes
XD-1526 Removed protobuf-java from dirt classpath

- this was introduced by changing to hadoop22 as default

- need to use the protobuf jar provided by each distro

- updated cdh4 to version cdh 4.6.0
XD-1521

Introduce constant for xd.stream.name and the like

Rename xd.stream.name to xd.job.name

Expose container info under xd.container.*

Address review comments
Remove hadoop cp version/distro log
XD-1528 Singlenode external batch db support

- Add HsqldbServerProfileActivator initializer in SingleNodeApplication's adminContext
  -  This initializer activates the hsqldbServer profile (which manages lifecycle operations on HSQLServerBean) only when the hsqldb datasource and embedded hsqldb are selected
  - Intrduced `singlenode.embeddedHsql` property that sets the option to use embedded hsqldb in case of singlenode server
    - Updated config/servers.yml for the same property to override in case of non-embedded hsqldb
using regex to split deployment properties

added unit test
XD-1530 Reverting to use deprecated FileStatus.isDir() method

- This is necessary to remain compatible with Hadoop 1.x versions
XD-1533: Clean up failed deploy attempts

If a container fails to deploy a module, the admin needs to clean
up the /xd/deployments/modules/CONTAINER-ID/module path so that
another attempt can be made to deploy that module to that container.
XD-1532 Unregister MBeans on module start() failure

- When the module start() life-cycle method fails, the registered MBeans for the module should
be unregistered so that when the module gets deployed again, it won't see a duplicate MBean
   - Catch BeansException on module start() and destroy the context if exception thrown
      - Fixed on both SimpleModule and ComposedModule
Update stream create message

- Shell command will return "Created and deployed" in case of stream creation with deploy
  - otherwise, command will return "Created"
suppressing xd-singlenode shutdown traces
XD-1539 avoid stacktrace on xd-container shutdown
XD-1540: Stacktrace on xd-admin restart

Fixed race condition between StreamListener and ContainerListener.

Upon buildup of the stream deployment cache, the listener fires
which causes the streams to be deployed. At around the same time,
the container shows up which causes its listener to try to deploy
a stream to it. The stream listener was the first to write
the deployment path thus causing the subsequent NodeExists exception
in ContainerListener.