Assert on the queue name, not the endpoint name, and untag Bug_2307 (GH-3827)

[jeremydmiller]

Closes #3827.

This was never a product bug, contrary to how I filed the issue — I inherited the diagnosis from the in-file note instead of reproducing it first. Correction is on the issue too.

Bug_2307_batching_with_conventional_routing carried [Trait("Category", "Flaky")], excluding it from CIAzureServiceBus. The note said the listener's "EndpointName is just the raw type name rather than the sanitized queue name — a naming bug in the GH-2307 fix".

Dumping every Azure Service Bus endpoint the convention builds says otherwise:

EndpointName='Wolverine.AzureServiceBus.Tests.Bugs.BatchedItem'
Uri='asb://queue/wolverine.azureservicebus.tests.bugs.batcheditem'   <- correctly sanitized
IsListener=True

The listener exists and its Azure Service Bus entity name is correct. GH-2307 works end to end; nothing is misnamed on the broker.

EndpointName is a logical label that deliberately is not the entity name:

• MessageRoutingConvention has endpoint.EndpointName = queueName commented out on both listener-creation paths.
• The transport's own system endpoints behave identically — AzureServiceBusResponses → asb://queue/wolverine.response.*, AzureServiceBusRetries → asb://queue/wolverine.retries.*.
• AzureServiceBusQueue.QueueName is the physical entity name, assigned once at construction; EndpointName is mutable and picks up the friendly value afterwards.

So the test was asserting on the wrong property. It now asserts on QueueName — the thing GH-2307 is actually about — and the Flaky tag comes off.

Verification

• 3/3 passes in ~5s against the emulator
• Full wolverine.slnx Release build clean, 0 warnings

The class returns to CIAzureServiceBus.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WHAuhdWS3XeAk16swV9G8m