Fix JSF memory leak

This is not a great fix, but I can't see any other
way to do it unless JSF fixes their crappy injection SPI
[WFLY-1392] use JAVA_HOME to locate jconsole executable.
Upgrade JBoss LogManager
JBTM-1747. Add XTS dependency to the JBossWS module
JBTM-1830 Update to fix the special character in the byteman script path
JBTM-1364. REST-AT to JTA bridge integration
WFLY-1808. Update transaction API 1.2 to 1.0.0.Beta1
WFLY-1892 Upgrade Narayana to 5.0.0.M4
JBQA-7126 Remove BMScript.java (resolved via merge conflict)
WFLY-1996 Fix app client not starting when running single jar
[WFLY-490] Shut down controller service properly even in test setups
[WFLY-490] [WFLY-1915] RBAC config domain propagation
[WFLY-490] [WFLY-1985] tests for read-attribute leaking sensitive data
[WFLY-490] [WFLY-1985] fix for read-attribute leaking sensitive data
[WFLY-1907] / [WFLY-490] The whoami operation needed the reply type setting so that it would be represented correctly in the JMX facade.

This commit now sets the return type to String, although previously no return type had been specified clients have been identified that are dependent on the return type being a String.
[WFLY-430] / [WFLY-490] Update the whoami operation so that it outputs the mapped roles for the current user if verbose=true and the current access control provider supports role mapping.
[WFLY-490] [WFLY-2000] Properly deal with undefined provider on rollback
[WFLY-490] Beef up managed domain RBAC test suite
[WFLY-2009] rethrow IOException in org.jboss.aesh.console.Console constructor as CliInitializationException
[WFLY-2014] @Ignore unstable test