RabbitMQ - migrate transient_nonexcl_queues to durable queues or exclusive transient queues

Rabbit 4.3+ dropped support for transient_nonexcl_queues, which is the type of queues OSIE is trying to create (the feature has been deprecated since 2021 - https://www.rabbitmq.com/release-information/deprecated-features-list, but up until 4.3 RabbitMQ only threw warnings into log, now it rejects them).

This can be worked around by setting deprecated_features.permit.transient_nonexcl_queues = true in RabbitMQ cluster configuration, however it’s not a permanent fix since the the feature will be removed in future RabbitMQ versions.

Documentation at https://www.rabbitmq.com/docs/queues#durability recommends switching to different type of queues:

Transient (non-durable) non-exclusive classic queues are deprecated and cannot be declared by default starting with RabbitMQ 4.3.0.
Please use one of the following:
- durable queues
- non-durable exclusive queues
- durable queues with a queue TTL (a reasonably close equivalent to non-exclusive transient queues)
To explicitly allow transient non-exclusive queues, add the following line to rabbitmq.conf:
Enables deprecated non-durable (transient) non-exclusive queues
(disabled by default as of RabbitMQ 4.3.0, will be removed in a later version)
deprecated_features.permit.transient_nonexcl_queues = true

Do you plan on implementing this in the future in order to not run into problems when upgrading to newer RabbitMQ version in the future?

Thank you.