Suppress ReSharper nullability errors in Mocha

[glen-84]

Summary of the changes (Less than 80 chars)

• Suppress ReSharper nullability errors in Mocha.

[Copilot]

Pull request overview

This PR suppresses ReSharper nullable-contract inspections in Mocha where the code performs null checks on members that are declared non-nullable, reducing IDE noise during development.

Changes:

• Added ReSharper ConditionIsAlwaysTrueOrFalseAccordingToNullableAPIContract suppressions around null checks in transport description building.
• Added the same suppressions around outbound route lifecycle checks (Endpoint is null) during initialization/discovery.
• Added suppressions in routing/indexing logic when checking endpoint addresses for null.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 8 comments.

File	Description
src/Mocha/src/Mocha/Transport/MessagingTransport.cs	Suppresses ReSharper warnings around null checks for receive/dispatch endpoint resources in Describe().
src/Mocha/src/Mocha/Transport/MessagingTransport.Lifecyle.cs	Suppresses ReSharper warnings around outbound route endpoint-null checks during setup/discovery.
src/Mocha/src/Mocha/MessageTypes/OutboundRoute.cs	Suppresses ReSharper warning around Endpoint null check in Describe().
src/Mocha/src/Mocha/Endpoints/EndpointRouter.cs	Suppresses ReSharper warnings around address-null checks while updating the endpoint address index.

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (71cedc3) to head (d52d852).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@     Coverage Diff      @@
##   main   #9545   +/-   ##
============================
============================

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[glen-84]

@Copilot What do you think about your own review here?

I think the review was directionally thoughtful, but not well calibrated for this PR.

The core idea in the comments on ReceiveEndpoint.Source and DispatchEndpoint.Destination was reasonable: if something is genuinely nullable in supported use, the type system should say so. But in this case it pushed too hard toward “make the API nullable” and didn’t weigh the cost of widening a public contract just to silence a ReSharper warning. For a PR titled “Suppress ReSharper nullability errors in Mocha,” that’s too big a design leap.

What I’d say now is:

The review found a real tension between lifecycle state and nullability annotations.
It overstated the best fix. Targeted suppression was a better answer than changing public nullability.
I’d downgrade it from a design concern to a tooling/lifecycle note: “the analyzer can’t model this lifecycle cleanly; localized suppression is acceptable here.”
So my take is: useful instinct, wrong recommendation.