[WFLY-3255] Fix the value-type description for the SimpleListAttributeDefinition.
[WFLY-3255] Update Infinispan model version
[WFLY-3255] Update JGroups model version
[WFLY-3255] Update logging model version
[WFLY-3255] Update core model version
WFLY-3361 Remove empty xmlns attributes from server configs on IBMJDK.

This empty xmlns attributes  (xmlns='') produced by XSLT transformation on IBM JDK
cause parsing exceptions on server startup.
[WFLY-958] Messaging: enforce security for in-vm connections

* add override-in-vm-security attribute to hornetq-server.
  Default value is true to keep the same behavior (ie in-vm connections
  overrides the security credentials). Setting it to false means that
  messaging code using in-vm connections *must* have valid user
  credentials (i.e. JMS createSession() without user/password will
  fail).
* bump messaging extension management version to 3.0.0
* bump messaging XML namespace to urn:jboss:domain:messaging:3.0
* add transformation test for messaging 3.0 XML
* add messaging-2.0.0.dmr to subsystem-test framework

JIRA: https://issues.jboss.org/browse/WFLY-958
increase surefire PermGen size to 256MiB
Upgrade xnio to 3.3.0.Beta1
[WFLY-3377] Infinispan cache container statistics configuration does not propagate to caches
Merge pull request #6259 from jmesnil/WFLY-958_enforce_security_invm_connections

[WFLY-958] Messaging: enforce security for in-vm connections
Merge pull request #6265 from jamezp/WFLY-3255-b

[WFLY-3255] Fix the value-type description for the SimpleListAttributeDefinition.
Merge pull request #6273 from zebrik/WFLY-3361

WFLY-3361 Remove empty xmlns attributes from server configs on IBMJDK.
Merge pull request #6286 from ctomc/undertow

Upgrade xnio to 3.3.0.Beta1
Merge pull request #6293 from rhusar/WFLY-3377_statistics_take2

[WFLY-3377] Infinispan cache container statistics configuration does not...
WFLY-3175 Create non-clustered implementations of org.wildfly.clustering.api services

This reverts commit b38bd496d8bdb6834f02717e12995d9031d4de88.
WFLY-3180 OOMs are still possible when using clustered web sessions/SFSBs w/passivation

This reverts commit 2d7bca2739afefb5e1efdc4971e25e3113a69fbc.
Ensure expiration is always scheduled on the owning node.
This prevents the possiblity that an session or bean might expire prematurely if routing/affinity is not respected.