[WFLY-1286] Support injection of JMSContext

* add a CDI extension providing a producer for injected JMSContext
  resources
* add a Phase.DEPENDENCIES_JMS phase to add a dependency to the
  org.jboss.as.messaging module for Weld deployments (so that they can
  access the JMSContext producer) and a
  Phase.POST_MODULE_JMS_CDI_EXTENSIONS to provide a JMSContext producer
* wrap the injected JMSContext to restrict used of methods (JMS 2.0
  spec, §12.4.5)
WFLY-1791 :  Adding test to close the bug "Unable to use Filter Expressions in filter-spec"
WFLY-1809 Remove usage of deprecated Infinispan API from the security subsystem
WFLY-1794 CDI JSF apps get WELD-001529 warning
[WFLY-191] Handle special characters in dir path

Make sure the path to vault keystore is decoded before using.
[WFLY-191] Decode URL file path in arq test
[WFLY-1710] XA recovery warning after HornetQ fail-back

When a HornetQ server is deactivated (after a backup server has failed
over and the original live server is restarted), remove the
corresponding HornetQActivationService (instead of flagging it as
PASSIVE) so that all dependents services are stopped.

Add a HornetQActivationService dependency to the
ResourceAdapterActivatorService started in
PooledConnectionFactoryService.createService()
flag HornetQServerResource's service controller as volatile
WFLY-1753 Component upgrade to Jipijapa 1.0.0.Alpha5 to address management NPE in Hibernate statistics integration code
WFLY-1781 XTS subsystem doesn't list the DUP phase order in Phase.java
[WFLY-1796] simplify write connector attribute

For backwards compatibility, the connector attribute (used in the
messaging subsystem's connection-factory & pooled-connection-factory)
must be a map where the key is a connector name and the value is not
taken into account (in previous HornetQ versions, the value was the
backup's server connector).

This is a source of confusion when creating resources with connector:
users expect to pass a list of connectors and this fails as they must
pass a map with undefined values.

This corrector will replace a list with the map expected to populate the
model.
WFLY-1810 SFSB tx lock not released in exception was thrown in Synchronization callback
[WFLY-490] [WFLY-1818] Allow ModelControllerClient creator to disable JBOSS_LOCAL_USER SASL mechanism
WFLY-1654 Register WeldTerminalListener
WFLY-1841: upgrade to aesh 0.33.7
[JBCTS-1318]:Add javax.api dependency to enable javax.net.ssl.SSLPermission
Make 'prog' overridable

The prog name for jboss is 'hard coded' to be 'jboss-as', however when integrating JBoss on its system
one my prefer to use a custom script and override the name (to name 'jboss-eap' for instance or use
the name of the application, when it is only running one application). The variable 'prog' has been
therefore renamed PROG and has become overridable, like the other JBOSS_...
Rename PROG variable to JBOSS_PROG_NAME:

As PROG is a pretty generic name, and as it can now be overriden from outside
the script, it seems appropriate to prefix it with JBOSS_, like the other overrideable
names in the script, but also append _NAME to make the variable name more meaningful
s/jboss-as/Wildfly/ for prog name
fix intermittent failure on InjectedJMSContextTestCase

* clean up all JMS resources (queues, temp queues)
* ignore messages redelivered to the MDB
* use a JMSQueueDefinition instead of the CreateQueueSetupTask
  to deploy the JMS queue required by the test