fix(test): propagate xUnit cancellation

Merged
RE
2mo ago
+9331-4654

Problem

The test build globally suppressed xUnit1051, so Microsoft Testing Platform and xUnit cancellation did not consistently reach long-running waits, lifecycle operations, storage calls, streams, reminders, transactions, and provider test helpers.

Solution

  • remove the xUnit1051 suppression and propagate TestContext.Current.CancellationToken throughout the test suites
  • add cancellation-aware TestingHost, persistence, reminder, transaction, durable-job, streaming, and test-grain helper APIs
  • pass cancellation through cluster lifecycle and provider operations, including file storage async I/O
  • update the generated TestingHost API surface for the new overloads

Rationale

Cooperative cancellation now reaches the operation performing the work, allowing stopped or timed-out test runs to terminate promptly while preserving existing timeout and cleanup behavior.

Microsoft Reviewers: Open in CodeFlow