[WFLY-1712] Stop the name attribute from being added when adding handlers/subhandlers.
Upgrade byteman to 2.1.4 (latest)
[WFLY-2061] Use runtime name when finding deployment service to read status
WFLY-2697 Base64 encode inter-process messages sent over stdin
[WFLY-2171] Use deployment unit processors to register mod_cluster metrics
[WFLY-2090] Rework metrics to be HttpHandlers instead of ThreadSetupActions since they can run multiple times and cause ISE
[WFLY-2171] Introduce UndertowAttachments class to shelter homeless AttachmentKeys used for mod_cluster integration
[WFLY-2171] Rework running requests metric into a HttpHandler
[WFLY-2171] Only register the metrics that are actually configured to be used
WFLY-2651 If there is a transaction active when the setup action first runs don't attempt to close it
WFLY-2728 Handle wrapped request and response objects
WFLY-2725 Ignore Class-Path entries that are just a '.'
[WFLY-215] Clustering tests leave a hanging instance if they are run in opposite order
WFLY-2743 Make sure all access to the ServiceRegistry is guarded by appropriate permission checks
[WFLY-2730] HTTP upgrade multiplexing

When the HTTP upgrade handshake is performed, check whether
the http-upgrade-endpoint is defined and accepts the handshake
only if its value matches the acceptorName.
This http-upgrade-endpoint header is used by a http-connector to
specify which http-acceptor must be used in case there are multiple
http-acceptors registered on the server.

If the http-upgrade-endpoint header is not present, the 1st http-acceptor
encountered will be used. This is not deterministic and is suitable only
if there is a single http-acceptor.

* remove native messaging port for messaging subsystem.xml configuration
and use http-connector for JMS RemoteConnectionFactory
* add a http-connector-throughput to replace the corresponding
  netty-throughput

JIRA: https://issues.jboss.org/browse/WFLY-2730