RequestMessageHeaderMatcher with MatchBehaviour.RejectOnMatch reverses match results twice

[flts]

Describe the bug

Following the Reversing the match behaviour with MatchBehaviour.RejectOnMatch
example the reponse will always be Unauthorized even if a correct header is added on the request.

I believe the following line shouldn't call MatchBehaviourHelper.Convert() again as it is already called for each Matcher. Other RequestMessage***Matcher's do not call MatchBehaviourHelper.Convert() before returning.

WireMock.Net/src/WireMock.Net/Matchers/Request/RequestMessageHeaderMatcher.cs

Line 138 in be4b0ad

return MatchBehaviourHelper.Convert(_matchBehaviour, MatchScores.ToScore(results, MatchOperator));

Expected behavior:

Given the following example taken from the docs. The expected behavior is that only an Unauthorized response is returned when the header api-key is missing from the http request.

server
   .Given(Request.Create()
             .WithPath("/needs-a-key")
             .UsingGet()
             .WithHeader("api-key", "*", MatchBehaviour.RejectOnMatch)
             .UsingAnyMethod())
   .RespondWith(Response.Create()
             .WithStatusCode(HttpStatusCode.Unauthorized)
             .WithBody(@"{ ""result"": ""api-key missing""}"));

Other related info

Since WireMock.Net v1.5.0.