Fixed issue with headers exchange matching does not mimic normal Rabb…

[everttimmer1963]

…itMQ.Client behavior.

The regular client does not evaluate x-... headers when 'all' or 'any' was applied. It uses 'all-with-x' or 'any-with-x' for that.

The mocking library did not check for the 'x-...' filters when matching, and checked all headers, including the x-... headers.

[Copilot]

Pull Request Overview

This PR aligns the mock library’s headers exchange matching behavior with the official RabbitMQ.Client by introducing “all-with-x” and “any-with-x” modes, ensuring ‘x-’ prefixed headers are handled correctly by default and only considered when explicitly requested.

• Support for “all-with-x” and “any-with-x” match modes in both queue and exchange matching methods
• Updated header filtering logic to exclude ‘x-’ headers for the default “all”/“any” modes
• Version bump to 1.2.5 and release notes update

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
RabbitMQ.Client.Mock/Server/Exchanges/HeadersExchange.cs	Add “all-with-x”/“any-with-x” options and filter ‘x-’ headers appropriately
RabbitMQ.Client.Mock/Releasenotes.txt	Add entry for header-matching bug fix in 1.2.5 release
RabbitMQ.Client.Mock/RabbitMQ.Client.Mock.csproj	Bump package version from 1.2.4 to 1.2.5

Comments suppressed due to low confidence (1)

RabbitMQ.Client.Mock/Server/Exchanges/HeadersExchange.cs:126

• New 'all-with-x' and 'any-with-x' behaviors introduce additional branching; please add unit tests covering these scenarios to ensure correct header matching.

if (match.Equals("any") || match.Equals("any-with-x"))