migrate to jboss-cli vs scripts for creating/deploying xPaaS images

Currently xPaaS images are configured via direct manipulation of the `standalone-openshift.xml` file and the use of markers in this (non-functional/transient) configuration file.

I'm suggesting the recommended practice of configuring via the admin cli (jboss-cli) should be used to introduce further changes and as a migration from the current scripts.

Some of the benefits include:

• all administrative configuration tasks are available via the admin cli will allow changes to the full extent of the xsd defining the subsystem(s).
• consistent approach to administrating the subsystems.
• environmental variable substitution can be introduced within the .cli scripts.
• remove the dependencies/limitations of the bash scripts.

Some current examples of using jboss-cli for configuration (hacking the current launch script):
https://access.redhat.com/solutions/3402311
https://access.redhat.com/solutions/3402171