Rename JBoss AS to WildFly

- renames name in pom.xml
- renames build result folder / zip
- renames output of started server
- renames in README
Tweak properties a bit so not every pom has full distro path but common variable
JBoss -> WildFly
[WFLY-1278] Upgrade HornetQ to 2.3.0.Final
upgrade metadata to latest version.
Upgrade EE7 APIs (CDI API, Interceptors 1.2 API)
AS7-6558 Initial CDI 1.1 support (Merged Weld 2 subsystem from https://github.com/weld/as7-weld-subsystem)
Added workaround for http://java.net/jira/browse/JAVASERVERFACES-2837
fix intermittent failures

leave some time after HornetQ server is activated before checking its
resources.
do the same after the :reload operation to avoid a false positive if the
server has not changed its server-state from running.

We had some failures in our integration server because the test was
checking a queue after the server activation while the queue was
installing (and not ready to handle a :read-attribute operation).
AS7-6790 Multi-JSF doesn't understand new modules structure.
[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-SNAPSHOT

* exclude the JMS 1.1 spec artifact from
  org.jboss.ws.cxf:jbossws-cxf-server dependencies
[WFLY-509] JMS 2.0 API support

add SimplifiedJMSClientTestCase test for new JMS 2 simplified API using
an injected JMSContext (@Ignore until injection works)
[WFLY-509] JMS 2.0 API support

* add CDIExtensionProcessor to be able to support injection of HornetQ's
  JMSContext