allow additional consume options

[jfromaniello]

Related to the issue I described in #23 . This change allows me to create a client using the pseudo-queue amqp.rabbtimq.reply-to like this:

  const client = new AMQPRPCClient(connection, {
    requestsQueue,
    repliesQueue: 'amq.rabbitmq.reply-to',
    consumeOptions: {
      noAck: true
    }
  });

The noAck option when calling consume is required. Messages from this special queue can't be ack'ed.

[jfromaniello]

I rebased this change into master.