[AS7-6699] HornetQ backup mode

When HornetQ is configured to be a backup, it will start and remain
passive (its resources are not deployed, it does not accept any
connections, etc.)

For AS7 hornetq-server's children resources, that means that:
* read-attribute on runtime attributes is a no-op (returns undefined)
* execute an operation on a queue will throw an exception warning the
  user that HornetQ is in backup mode
* add active runtime r/o attribute to hornetq-server

For AS7 services, there are some substantial changes too.
HornetQService default does *not* start the HornetQ server. This is done
by JMSService. This means that any service must not depend on
HornetQService but JMSService to make sure that the server is
effectively started.
JMSService is started asynchronously and the server start is completed
when:
* the HornetQ server has been activated (immediately when it is a live
  node, or after failover if it is a backup)
* and the JMSServerManager is started (and can deploy JMS resources)

It is important for other services depending on messaging services
(queue, jms-queue, topic, connection-factory &
pooled-connection-factory) that these services must NOT be started
until a backup hornetq-server fails over.

* refactor messaging's SecurityActions (based on ExtensionAddHandler
  snippet)
AS7-6652 Add ability to customise timer SQL based on database type
AS7-6786 Hibernate test cases do not close the session factory
Potential OOM fix
[AS7-6722] Best attempt to process overridden directory properties in scripts. None of the scripts allow for directories with spaces.
Change test to not rely on text in the error pages
First try of getting undertow in core AS

* webservices subsystem does not compile
* osgi does not compile
* modcluster does not compile

this three subsystems are disabled for now

make arq work again

More undertow fixes

fix resolving socket binding

fix default configs

only use client api

add xsd and temporary disable few testsuites

fix import dependancies

change tests to look for subsystem=undertow instead of subsystem=web

fixes after rebase
sync with subsystem
sync with subsystem
fix managed domain
proper xsd
improve xsd and use proper schemas
upgrade to servlet spec 3.1
Minor update to test utility to check if the server has actually sent a response before trying to use it, corrects a NullPointerException that was masking real failures.
fix root context test
Fix few Tests
fix default config
Don't use the status code of 401 as that is specifically used when sending a challenge to the client, 403 is better suited where the request reaches the resource but we still choose not to fulfil the request.
Rename io.undertow module to io.undertow.core
fix few tests