Fix late binding of route destinations in mocha

[PascalSenn]

No description provided.

[Copilot]

Pull request overview

Fixes a routing bug where an outbound route with an explicit destination could be “claimed” by convention-based handler matching (when handlers are explicitly bound), causing sends to go to the conventional endpoint instead of the configured destination queue.

Changes:

• Added regression tests for RabbitMQ and InMemory ensuring an explicit Send(...To*Queue(...)) destination wins even when the same message type is handled via an explicitly bound endpoint.
• Updated shared transport lifecycle route discovery to avoid connecting outbound routes that already have an explicit Destination, allowing the build-time destination-connection pass to bind them correctly.
• Minor cleanup: avoid redundant ConnectEndpoint after ConnectRoute.

Reviewed changes

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

File	Description
src/Mocha/test/Mocha.Transport.RabbitMQ.Tests/Topology/RabbitMQMessageTypeExtensionTests.cs	Adds a regression test asserting Send routes bind to an explicit RabbitMQ queue destination even with explicit handler binding.
src/Mocha/test/Mocha.Transport.InMemory.Tests/InMemoryHandlerClaimTests.cs	Adds the equivalent regression test for the InMemory transport.
src/Mocha/src/Mocha/Transport/MessagingTransport.Lifecyle.cs	Prevents explicit-destination outbound routes from being claimed during endpoint discovery / handler matching, fixing late-binding behavior.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.