Only allow one transient "tick" process per quorum queue

[kjnilsson]

Quorum queues execute metrics emission and other periodic tasks by default every 5000ms. This is done in a separate one-off process. Some of the work done queries the queue process itself as well as each node in the quorum queue membership. If this takes more than the tick interval we may end up running multiple of these tick processes as the same time. During times of great load this could potentially cause runaway process use when there are lots of quorum queues in a system.

We should find a way to ensure each queue only ever runs a single of these tick processes at any one time. Possibly by using node local locking, aux state or name registry.

[SimonUnge]

Would a similar approach as rabbit_stream_coordinator aux approach suffice, by keeping track of the pid and when the pid dies?