rabbitMQ support for extra arguments

Note: see updates below; if your rabbitmq is asking for extra arguments for a queue that already exists, first try setting loader.messaging.settings.autocreate.objects=false in grouper-loader.properties

If we have an existing rabbitMq queue with feature arguments `x-queue-type: quorum`, the grouper messaging system fails with an error:

com.rabbitmq.client.ShutdownSignalException: channel error; protocol method: #method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg 'x-queue-type' for queue 'grouperChangeLog' in vhost '/midPoint': received none but current is the value 'quorum' of type 'longstr', class-id=50, method-id=10)

When the Grouper rabbitmq messaging system creates a channel, it passes null in the extra arguments field. If we could add extra properties in the loader config, and then send them with the channel, this would fix the issue (tested and confirmed).

E.g.

changeLog.consumer.rabbitMqMessaging.queueArgs.0.key = x-queue-type

changeLog.consumer.rabbitMqMessaging.queueArgs.0.value = quorum