StompBrokerRelay: Adapt to RabbitMQ deprecation of transient, non-exclusive queues

[acutus]

spring-messaging:6.1.12

RabbitMQ has deprecated transient, non-exclusive queues (see rabbitmq/rabbitmq-server#13009 and https://www.rabbitmq.com/release-information/deprecated-features-list).

StompBrokerRelay (StompBrokerRelayMessageHandler?) should consider this when creating STOMP-subscriptions and switch to durable client-named queues as a default, instead of the current transient non-exclusive queues created for subscriptions.

[artembilan]

The deprecation warning from STOMP plugin in RabbitMQ is going to be addressed in version 4.2 this Fall: rabbitmq/rabbitmq-server#13016.

Meanwhile a {"durable", "true"} header can be set from the application on send and subscribe commands.

Nothing to do from the Framework perspective.

[sbrannen]

Thanks for the research and feedback, @artembilan!

In light of that, I am closing this issue.