Configure a NATS JetStream stream with WorkQueue retention for single-consumption FIFO job distribution

Steps

1. Create a stream and set its retention policy to WorkQueuePolicy (as opposed to the default LimitsPolicy or InterestPolicy)
2. Understand that WorkQueuePolicy enforces FIFO-style, consume-once semantics: each message is automatically deleted from the stream as soon as it is acknowledged by a consumer
3. Create only consumers whose subject filters do not overlap on a WorkQueue stream — the server enforces at most one consumer per subject on this stream type, since overlapping consumers could both claim the same message
4. Bind one or more worker processes to the same non-overlapping consumer (using a pull consumer with multiple pullers, for example) to distribute the FIFO workload among them while each message is still processed exactly once
5. Set upper-bound limits (MaxMsgs, MaxBytes, MaxAge) alongside WorkQueuePolicy if desired; these limits are additive/enforced on top of the work-queue consumption behavior, not a replacement for it
6. Ack each message promptly after processing so the stream storage doesn't grow unbounded waiting on unacknowledged messages