Netty Direct Buffer warning fix

When deploying Wildfly 8.x, you'll see this in the server.log:
```
INFO [io.netty.util.internal.PlatformDependent] Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to av
oid potential system unstability.
```
Following this into netty, here:
https://github.com/netty/netty/blob/master/common/src/main/java/io/netty/util/internal/PlatformDependent.java#L581
Down to here:
https://github.com/netty/netty/blob/netty-4.0.15.Final/common/src/main/java/io/netty/util/internal/PlatformDependent0.java#L82

We need access to sun.misc to see if direct buffers are available.
WFLY-3829 linux
Update module.xml

Added javassist after inspecting io.netty log messages as "FINE" level after Wildfly startup and seeing additional information from netty requesting javassist for performance.
Update module.xml

Add optional flag to javassist as this is part of Wildfly-core
WFLY-3443 JCA tracking should default to false for datasources
WFLY-3864 Upgrade Weld to 2.2.5.Final
[WFLY-3827] - Update Subsystem for PicketLink Console.
WFLY-3848 Upgrade JGroups to 3.4.6.Final
WFLY-3844 invlidate the principal cache on logout
WFLY-3221 Enable flushOnSessionInvalidation support
WFLY-3869: Add test scenario with taglib from module only.

This extends test coverage for WFLY-1172.
[WFLY-333][BZ-1126287] add a test for the wait-time statistic

Adjust timeout per Jason's comment

increase timeout
Merge pull request #6733 from clebertsuconic/master

https://issues.jboss.org/browse/WFLY-3874 - update hornetq to 2.4.4
WFLY-2772 Leverage JGroups FORK to consolidate EE channels
Fix deprecated usage of HttpClient API.
Merge pull request #6697 from stuartwdouglas/WFLY-3844

WFLY-3844 invlidate the principal cache on logout
Merge pull request #6732 from zebrik/master

WFLY-3869: Add test scenario with taglib from module only.
Merge pull request #6723 from jharting/WFLY-3864

WFLY-3864 Upgrade Weld to 2.2.5.Final
WFLY-3189 - Do not use schema location in schema element. Do not use
schemaLocation when importing a namespace.

XML validators seem to get confused when schema location is specified
and imports / includes are circular. Instead rely on entries in XML
catalogue.

WFLY-3189 - retaining version attribute
Merge pull request #6739 from robstryker/WFLY-3189a

WFLY-3189 - Do not use schema location in schema element.