AMQPLib: Allow queue and durability to be part of the configuration

[shadyvd]

Why?
In AMQP mode, Ascoltatori creates a queue using an asc_${uuid()} as the name every time it is initialized. Also, it checks to ensure that the queue is not durable.

What is the problem?
The new queue(s) are not bound to an exchange, or a routing key - since that is not part of the standard configuration. Which means, in turn, that the Administrators have to do something to ensure that each new queue is bound to an exchange with a routing key. In large scale systems, this is obviously not an option.

What does this PR do?
Very simply, it allows for the name and durability of the queue to be specified as part of the configuration for AMQPLib.

Benefits
RabbitMQ Administrators can now ask the DevOps folks to use a specific queue as part of the deployment process.

So, for example, if there is a cluster of servers that use a specific Exchange / Queue combination for receiving logs, audit trails, etc., they will all use the same queue with the same routing key. This allows for round-robin message dispatch by a "topic" exchange - essentially, a load-balanced use-case.

[coveralls]

Coverage remained the same at 92.853% when pulling e6f696a on shadyvd:master into bc72263 on mcollina:master.

[coveralls]

Coverage remained the same at 92.853% when pulling 91a6bd4 on shadyvd:master into bc72263 on mcollina:master.