Prevent quorum queues from being server-named

[michaelklishin]

Server-named quorum queues make no sense, as their rationale hopefully explains. They create interesting problems when used. We should prohibit this combination, as we already do for certain "transient state" features in the context of quorum queues.

Per discussion with @kjnilsson.

[dcorbacho]

We will wait to fix this issue until stream queues are merged, as we can use the new queue types to query queue capabilities and make it generic.

[avatarofhope2]

I don't understand the rationale or the problems, but would like to comment here to potentially find an alternative for my use case. I'm trying to create a high availability cluster, and I use the RPC model documented here. If I should not use mirrored classic queues because of deprecation, and I cannot create server-named quorum queues, how should I properly implement RPC in a highly available way?

[mkuratczyk]

Have a look at this discussion: #6376 and if you have any questions - ask there.

The local random exchange could be an option once it's available.