AMQP-266/296/297 Allow Admin to Continue After Err

AMQP-296 Update Spring version to 3.1.3

AMQP-266 Add option to allow Admin to continue after exception.

Currently, if the Rabbit Admin hits an exception while declaring
Queues etc, it aborts the entire process. An exception can be
caused if, say, the 'x-message-ttl` attribute is mismatched with
that currently configured on the broker.

Add an option that allows declarations to continue after exceptions,
while logging (WARN) any exceptions encountered.

AMQP-297 Add RabbitAdmin.getQueueProperties()

Used in the above test to verify presence, or otherwise of
queues during Admin declarations.

Returns message and consumer counts for the queue.