fix(testing): isolate reminder event continuations
Problem
ReminderTestKit_StaleRefreshCannotRestoreUnregisteredReminder can resume directly on the LocalReminderService diagnostic-event thread after awaiting ReminderServiceStarted. The failed CI artifact shows the grain turn starting immediately and then waiting 30 seconds for its nested local reminder-service request, without reaching reminder storage. The existing Rx ToTask conversion permits synchronous caller continuations at this scheduler boundary.
Solution
Complete diagnostic event waits through task sources configured with RunContinuationsAsynchronously, while preserving replay, filtering, cancellation, error propagation, and subscription cleanup. Add a regression which verifies that a service-start waiter cannot run an ExecuteSynchronously continuation on the event emitter thread.
Rationale
Reminder diagnostic waits are phase barriers. Resuming consumers independently from the runtime event producer keeps subsequent grain calls outside the reminder-service scheduler turn and applies the same continuation guarantee already used by the observer's lifecycle-state waiters.
Fixes #10893