https://issues.jboss.org/browse/WFCORE-50 CLI tests using non-standard output stream don't reset the terminal when done
[WFLY-3169] Emit local JMX notifications

* Emit JMX notifications based on WildFly's own notifications
* Notification is supported for JMX connections either in-vm (through
  ManagementFactory.getPlatformMBeanServer() or WildFly's
  MBeanServerService) and remotely if the JVM is started with the remote
  monitoring and management
* WildFly remoting-jmx does not support JMX notifications
* WildFLy notification are converted to their idiomatic JMX
  counterpart
  * WildFly's attribute-value-written is converted to JMX's
    AttibuteChangeNotification
  * WildFly's resource-added and resource-removed are converted to JMX's
    MBeanServerNotifications *and* emitted by the
    MBeanServerDelegateMBean (like regular MBeans)

JIRA: https://issues.jboss.org/browse/WFLY-3169
WFLY-3292: adding phase values for reworked EE resource definition processors
Merge pull request #82 from jmesnil/WFLY-3169_local_JMX_notifications

[WFLY-3169] Emit local JMX notifications
Merge pull request #93 from aloubyansky/WFCORE-50-aesh-test-terminal

https://issues.jboss.org/browse/WFCORE-50 CLI tests using non-standard o...
Merge pull request #119 from emmartins/WFLY-3292

WFLY-3292: adding phase values for reworked EE resource definition proce...
Introduce an encapsulation of the various elements of the management model
Use it support the copy-on-write/publish-on-commit semantic for ops that make management model changes
[WFCORE-60] Add a registry for capabilities and requirements, modifiable via the OperationContext
[WFCORE-60] Add convenience ops to base add/remove handlers
[WFCORE-60] Add ability to register needed capabilities to the subsystem test infrastructure