Initial HTTP upgrade support for management operations

This commit adds support for multiplexing the remoting protocol over
the HTTP management port, removing the need for two seperate management
ports.

Port 9999 is now no longer present in the default config, and the
management client will attempt to connect via a HTTP upgrade by
default.
Temporarily add back native interfaces into the default config
WFLY-1332 Add support for handling compressed message stream for EJB invocations
[WLFY-509] JMS 2.0 API support

* update maven GAV for JMS API to:

  org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:1.0.0.Alpha1

* exclude the JMS 1.1 spec artifact from
  org.jboss.ws.cxf:jbossws-cxf-server dependencies

* exclude temporarily the JMS 1.1 spec artifact from
  org.hornetq:hornetq-jms-server and org.hornetq:hornetq-jms-client
  depedencies until HornetQ supports JMS 2.0
delete manualmode's jbossas-messaging-failover before copy

HornetQ failover is depending on the file system to lock a file.
I have seen PRs be aborted because HornetQ live server can not lock this
file to start (there is no timeout on this lock operation).
Deleting the directory ensures that the file system's lock (from previous
runs) is removed.
WFLY-1344 (fix by jaikiran adjusted to be compatible with other changes)
WFLY-1333: Fix default access log prefix value
Fix default value for access-log/prefix in subsystem tests.
Revert fix, but add a comment.
Use ModelFixer in subsystem test to deal with wrong legacy default
Refix tests.
First web 8 build.
Minor cleanup
Prevent spurious creation of permission objects in many cases when security manager checking is disabled
Add privileged utility methods for the most common privileged actions which avoids the need to use expensive doPrivileged and checkPermission calls
Move to the privileged methods on WildFlySecurityManager