Gate application result fields by protocol version

[KirschBluteX]

Fixes #1754.

Summary

Add a single typed response-emission boundary after handlers and filters for protocol-version-specific result properties.

• Legacy requests strip resultType and, for cacheable results, ttlMs and cacheScope, and emit a warning when application or filter code supplied them.
• 2026-07-28 and later requests preserve explicit values and add the required defaults (complete, 0, and private).
• The boundary edits freshly serialized JSON nodes, so shared result instances are not mutated across requests or protocol versions.
• Normal, cacheable, immediate alternate, and MRTR result paths retain their type metadata through emission.

The policy is strip plus warning: it keeps legacy wire responses schema-valid and makes application misuse visible, following the SDK's existing compatibility-warning convention without converting otherwise valid requests into errors.

Tests

• Full ModelContextProtocol.slnx Release build: 0 warnings, 0 errors.
• Core focused protocol-result tests: 7 passed.
• ASP.NET Core focused HTTP wire test: 1 passed.
• MRTR legacy backcompat regression: 1 passed.
• Core non-Docker suite: 2,359 passed, 4 skipped, 0 failed.
• ASP.NET Core non-Docker suite: 612 passed, 30 skipped, 0 failed.
• Docker Everything Server connection test passed. The unmodified sampling test fails before invoking the SDK sampling handler because it calls the removed trigger-sampling-request tool; the current v1 image exposes sampleLLM. A diagnostic rerun with only that tool name updated passed both Docker tests (2/2); no unrelated fixture change is included here.
• git diff --check and targeted dotnet format --verify-no-changes passed for the changed files. Repository-wide format verification still reports existing whitespace diagnostics in untouched files.