fix(testing): track reminder schedules per owner

Merged
RE
3mo ago
+94-33

The Azure reminder churn test could stall until its five-minute cancellation when reminder ownership changed while fake time was paused. The reminder test observer aggregated scheduling state by grain and reminder, so an old owner's tick could consume the new owner's armed-wait signal and prevent further clock advancement.

Track tick attempts, armed waits, and schedule versions per local reminder owner instead. Clock advancement now waits until every active owner is armed, and ownership removal releases any newly satisfied waiter. Regression coverage models overlapping old and current owners during a handoff.

This fixes the test harness synchronization race without increasing timeouts or changing Azure Table reminder behavior.

Microsoft Reviewers: Open in CodeFlow