[Proposition] A consumer should be able to bind multiple queues

A consumer is tied to only one queue in the current implementation, which is a "RabbitMqBundle / Thumper" limitation but not a rabbitmq one. I already implemented it based on php-amqplib, but before coding everything in this repo, I just wanted to check if it seems interesting to other people.

The advantage is quite clear for me: I've a lot of "stuff that are not really that important but must be done someday". For that, I like to have "generic consumer" that are coupled with multiple queues and handle message one by one, coming from any of theses queues. It's a way better scalable architecture as I can launch multiple of these generic consumer instead of launching many of each queue.

The one "problem" I have is to be sure that all the queues of a single consumer are connected to the same exchange, and that can be verified on compilation time.