Unique node id not properly set on multiplexed channel

The JBoss-specific subclass of JChannelFactory was not overriding all the overloaded variants of createMultiplexerChannel, including the one called by JBoss Cache. As a result the unique node id was not being set as additional_data on the underlying channel until after the channel was connected, which means other nodes in the cluster were unaware of the unique id.

A major side effect of this is that DistributedReplicantManager.lookupReplicants would only return replicants for the coordinator node. Thus smart proxies for clustered services will only be able to communicate with the coordinator node.

DRMTestCase has been updated to detect this sort of problem.