iOS alert activation can tap after the command deadline

[thymikee]

Problem

An alert accept/dismiss tap can land after the command's deadline. The last deadline guard runs before the synchronous coordinate tap (RunnerTests+Alert.swift ~131-143 → RunnerTests+Interaction.swift ~527-535). On a slow host the tap is synthesized late: CI job 107674012511 logged the activation point at about 56 s and XCTest's coordinate tap at 82.99 s, then ALERT_DEADLINE_EXCEEDED. The caller is told the command failed while the tap still lands.

The #2843 banner test (testAlertActivationDoesNotWaitOutANotificationBanner) proves XCTest's interruption handling was not consulted (RunnerTests+AlertObservationTests.swift ~124-128). It does not prove the tap landed before the deadline, which is why it failed there.

Required behavior

• Check the deadline immediately before the event is synthesized, and never tap after it.
• Keep the post-activation uncertainty response. Never retry an alert tap.
• Split the test so that "no interruption handling" and "confirmed before the deadline" are asserted separately.

Refs #2491, #2843.

[okwasniewski]

Checked the activation path at 34f2eb1dc while triaging this downstream.

The last Date() < deadline guard is already inside the withBoundedInteractionIdleTimeoutIfSupported closure in activateAlertButton (RunnerTests+Alert.swift), and between it and the event there is only activateElement → tapAt → performCoordinateTap → interactionCoordinate(...).tap() (tvOS branches are compiled out on iOS). No wait or query sits between the guard and XCUICoordinate.tap(), so moving the check any closer changes nothing measurable.

That means the 56 s → 82.99 s gap in job 107674012511 was spent inside XCTest's own tap() (coordinate resolution against the SpringBoard-owned alert window on a starved host), which a pre-synthesis check cannot prevent. The fix that satisfies "never tap after the deadline" is to synthesize the alert tap through the HID bridge (synthesizedTapAt / RunnerSynthesizedGesture.synthesizeTap), which does not resolve elements before posting, with the deadline checked at the synthesize call. The test split (no interruption handling vs confirmed before the deadline) stands on its own.