AMQP-309 Fix Listener Channel Issue

When an external transaction manager is assigned to the listener
container, the fix for AMQP-260 corrected a problem where the
listener's channel was not used by RabbitTemplates running on
the same thread.

This is required for operations performed by the template to
participate in the same transaction.

However, this was too encompassing in that this did not take
into account that the template might be configured with a
different connection factory.

Add a test to show the template with a different connection
factory incorrectly used the listener's channel.

Add code to only use the listener channel if the client is
requesting a channel from the same connection factory.

Also, do not fetch a connection in the case where the
consumer channel is used (actually a no-op because the
single connection is cached).

Improve debug log during channel registration:

    Registering consumer channelCached Rabbit Channel: AMQChannel(amqp://guest@127.0.1.1:5672/,1) from factory CachingConnectionFactory [channelCacheSize=2, host=localhost, port=5672, active=true]
Merge pull request #95 from garyrussell/AMQP-309

* garyrussell-AMQP-309:
  AMQP-309 Fix Listener Channel Issue