New consumer not receiving existing messages immediately

[everttimmer1963]

Fixed issue where message delivery isn't started immediately when consumer added on existing queue containing messages.

[Copilot]

Pull Request Overview

This pull request addresses the issue where a new consumer on an existing queue did not receive messages immediately by ensuring the queue notifies when a consumer is added.

• Added a call to _waitHandle.Set() in both message requeue and when a consumer is added.
• Updated the consume operation to notify the queue upon consumer addition.
• Introduced a new test to verify immediate message delivery.

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
RabbitMQ.Client.Mock/Server/Queues/RabbitQueue.cs	Added _waitHandle.Set() in RequeueMessageAsync and a new NotifyConsumerAdded method to trigger immediate delivery.
RabbitMQ.Client.Mock/Server/Operations/BasicConsumeOperation.cs	Updated consumer binding and invoked NotifyConsumerAdded to ensure prompt message delivery.
RabbitMQ.Client.Mock/Releasenotes.txt	Updated release notes to reflect the fix for immediate message delivery.
RabbitMQ.Client.Mock/RabbitMQ.Client.Mock.csproj	Updated version number to 1.2.4.
RabbitMQ.Client.Mock.Tests/ConsumerTests.cs	Added test to validate that messages are delivered immediately when a consumer is added.

Comments suppressed due to low confidence (1)

RabbitMQ.Client.Mock/Server/Queues/RabbitQueue.cs:128

• [nitpick] Consider renaming 'NotifyConsumerAdded' to 'NotifyConsumerAddedAsync' to more clearly indicate its asynchronous nature.

public ValueTask NotifyConsumerAdded()