feat(rabbitmq): configurable error/audit queue arguments

[twatson83]

What

Adds two new consumer options to @serviceconnect/rabbitmq, mirroring the existing queueArguments / retryQueueArguments hooks:

• consumer.errorQueueArguments?: Record<string, unknown>
• consumer.auditQueueArguments?: Record<string, unknown>

These flow into the error and audit queue declarations, so they can be declared with RabbitMQ arguments — e.g. as quorum queues:

consumer: { errorQueueArguments: { 'x-queue-type': 'quorum' } }

Why

The main and retry queues already accept arguments, but the error and audit queues were hardcoded as { queue, durable: true } with no arguments hook, forcing them to stay classic queues. This closes that gap so all four declared queues expose the same configuration surface.

Changes

• packages/rabbitmq/src/options.ts — new fields on the consumer interface and ResolvedConsumerOptions; default to {} in resolveConsumerOptions.
• packages/rabbitmq/src/topology.ts — spread the resolved arguments into the error and audit QueueSpecs.

The consumer already forwards QueueSpec.arguments to queueDeclare, so no consumer change was needed.

Compatibility

Backward-compatible: empty args resolve to arguments: {}, which queueDeclare treats identically to no arguments. No wire-format or C# master-parity impact (queue arguments are a broker concern, not part of the message contract).

Operational note: x-queue-type is fixed at declare time — an existing classic error/audit queue must be deleted before it can be redeclared as quorum.

Testing

• Added merge tests for both queues in topology.test.ts and pass-through/default tests in options.test.ts.
• All 82 rabbitmq unit tests pass; tsc --noEmit and biome check clean.

🤖 Generated with Claude Code