In the old JMSContainerInvoker there was a flag called "createJBossMQDestination"
which allowed the MDB to automatically create the JMS destination.

This has is no longer supported with the reworking of the metadata and changes to the MDB container.

To re-introduce this behaviour and resolve some of the issues we had with this feature (which lead
to it being disabled by default), the behaviour should be made pluggable via a deployer instead.

Issues this will resolve over the previous implementation:
1) The Destination will be removed at undeployment
2) The Destination construction method can be replaced by switiching the deployer, e.g. for different backend jms servers
including understanding rar specific activation config properties
3) The behaviour is not necessarily JMS specific, e.g. other inbound adapters could create their own destinations

The legacy "createJBossMQDestination" will still be checked when it exists.