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.