BZ-1146506 & HORNETQ-1287  Message does not expire when it is diverted to another queue

https://issues.jboss.org/browse/HORNETQ-1287
https://bugzilla.redhat.com/show_bug.cgi?id=1146506

Diverts were not setting the expiry message during any type of divert.
It seems this was an initial design decision but I don't see a reason why
expiry should be removed between routing and diverting.
Besides this we also fixed the case where the original queue wasn't set
during divert and expiry.
HORNETQ-1419 Server doesn't deploy JMS Objects

When starting a standalone server using 'bin/hornetq run' the server
starts up but the jms objects such as Connection Factories and
Destinations configured in hornetq-jms.xml don't get deployed.

The reason behind this is that the "Run" command (Run.java) starts
the JMSServerManagerImpl without passing in a default config file and
we no longer put the default config dir into the server classpath
with the new startup method.

The fix is add a <jms> entry into hornetq.xml pointing to the default
hornetq-jms.xml file and in the "Run" command we pass the config
(if it configured) to JMSServerManagerImpl so that it will deploys
all the JMS stuff during start up.
Merge pull request #1875 from clebertsuconic/upmaster

BZ-1146506 & HORNETQ-1287  Message does not expire when it is diverted to another queue
Merge pull request #1876 from gaohoward/master_HORNETQ-1419

HORNETQ-1419 Server doesn't deploy JMS Objects
added logging for activation of colocated backups
HORNETQ-1422 - use default cluster connection for auth

https://issues.jboss.org/browse/HORNETQ-1422

If the acceptor used to connect to by the cluster controller is not associated witha cluster connection we use the default and its security for authentication.
fixing examples

fixes configuration for new ha-policy configuration and slight tweak to the Shared Nothing Activation.