Added config option to allow disabling x-expires in getDelayQueueArguments

[cosminardeleanu]

I am using quorum and i noticed that the messages are deleted before they're moved to their destination queue.
By disabling the x-expires, my messages are no longer lost.

I think is considerate to have the ability to enable/disable delay queue expires, to avoid issues for users that use quorum.

Found other issue related -> #601

---

From the TTL documentation (/ttl):

This page describes the key difference for x-expires.

"Queues will expire after a period of time only when they are not used (a queue is used if it has online consumers). ... This controls for how long a queue can be unused before it is automatically deleted."

From the Quorum Queues documentation (/quorum-queues):

This page describes the core design that explains why the TTL behavior is different.

"Quorum queues are optimized for certain use cases where data safety is the top priority."
"Quorum queues have differences in behaviour compared to classic queues as well as some limitations that it is important to be aware of..."

When combined, these two pages explain that the "unused" criteria for Classic queues (which prevents deletion if messages are present) does not apply to the more robust, data-safe Quorum queues, which prioritize consistency and guaranteed cleanup.