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.
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
Replace ForkChannelService with ForkChannelFactoryService.
Fix javadoc
Replace tabs w/spaces.
Clean up controller client in test
WFLY-3185 Strip cluster name from node names
Centralize vault cleanup
Fix problem with filter initialization
Fix RunAs support for Servlet init() methods
Ignore test until undertow update
[WFLY-3898] Speed up LDAP tests - use InMemory partitions for the ApacheDS
WFLY-3900 Allow EJBContext to be injected by CDI
[WFLY-3535] Improve detection by also considering org.apache.cxf.impl module, which transitively pulls org.apache.cxf one
[WFLY-3905] Only execute POJO processor on WAR deployments
[WFLY-3600] Part 2: Properly deal with exception types which actively block cause initialization
WFLY-3913 HTTPS socket-binding definition always needed
Use buffersize that is configured/calculated for  buffer pool