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.
WFLY-3185 Strip cluster name from node names
[WFLY-3898] Speed up LDAP tests - use InMemory partitions for the ApacheDS
WFLY-3913 HTTPS socket-binding definition always needed
Use buffersize that is configured/calculated for  buffer pool
WFLY-3876 Porting to IJ 1.2.B4
WFLY-3929 WeldApplicationFactory does not override getWrapped()
[WFLY-3930] Upgrade PicketLink to 2.7.0.Beta2
WFLY-3801 Make sure NOT_SUPPORTED and REQUIRES_NEW are the only allowed SFSB lifecycle interceptor transaction attributes
[JBWS-3835] Add mechanism for restarting target container while running JBossWS tests
WFLY-3888 enhance timer logging, show the full timer information for ERROR and WARN.
cache the part of the string which is final and only replace the dynamic values.
WFLY-3934 TimerServiceImpl should use message patterns

When running an allocation profile on our WildFly AS instance debug
logging in `TimerServiceImpl` showed up. The problem is that
`TimerServiceImpl` unconditionally generates debug strings using string
concatenation.

 * use `#debugv` instead of `#debug` for debug messages that take
   arguments to avoid allocating strings in case when debug logging is
   disabled
 * put calls to `#getTimedObjectId` for debug strings in `if` blocks
   since it additionally allocates strings

Issue: WFLY-3934
https://issues.jboss.org/browse/WFLY-3934
Merge pull request #6779 from marschall/WFLY-3934
Merge pull request #6778 from asoldano/master