Question: is there any 'nats' alike queue-group possible now or in future?

Hi, I am impressed and eager to test out cote because of your mesh-like discovery features.

The only feature I am missing (or not might have found) is something called "queue-groups" in nats:

https://github.com/nats-io/nats.js#queue-groups

Say you have a publisher emitting an event. And you have some worker-groups running multiple processes for different concerns. Example:

- Group A running 5 workers
- Group B running 5 workers

A published event (or might be a request?) should be processed by only 1 A worker + only 1 B worker. And of course, the publisher won't know anything about groups or workers, just emitting "something.done" to anyone interested.

Start with cote’s existing mesh-like discovery and event/request entry points, then compare their delivery semantics with the nats.js queue-groups behavior linked in the issue. Done requires a maintainer-approved scope for whether grouped delivery is supported or should be designed; the payload names no implementation files or tests.

Written by the indexing model from the issue text.