Ensure control over AMQP connection and template

[olle]

For proper production readiness, it is required that this library does not act upon shared resources for an application context. The opposite is also important, there should be very little coupling between configurations of the AMQP resources for the application and the Query/Response library.

This means control over the AMQP connection, it's properties and the AMQP Template, through a factory, is probably required in order to introduce the Query/Response library as a well behaved component, into a production application.

[olle]

To give some more context to this issue.

I know about solutions, already running in production, where the pre/post publish/consume interceptors are depended upon heavily. Such apps usually configure a global RabbitTemplate with these custom adaptations, which may be conflicting with the requirements that the Query/Response library has.