[whoisaldo]

ConnectScreenTests.testTheStarCardFollowsALongSessionAndCloses is new in 0.3.4 and failed twice on busy CI runners, at two different steps.

1. The release head b7b4d25 (run 41689814100, iOS job), :63 "closed for good":
   • The card disappeared after Close at t=22.91 s, and XCTest terminated the app at t=23.04 s.
   • On relaunch the card was back: the starCardClosed setting hadn't been saved before the kill.
2. This PR's first head, bbe684c (run 41695596742), :58:
   • The coordinate tap on Close never registered, so the card was still there after 5 s.
   • That's a lost tap on a starved runner, like the keyboard tests' lost taps fixed in Wait for the keyboard bar's Ctrl value, and retry only a tap the PC never got #173.

The test now:

• taps Close and, if the card is still there after 5 s, taps once more, then asserts the card is gone;
• no longer relaunches the app right after Close.

That a closed card stays closed across launches is already a unit test: FeedbackTests.testATapThanksAndACloseRetiresTheStarCard (FeedbackTests.swift:190-211) builds a fresh StarAsk from the same store. The update-banner rule is also a unit test there. The app is unchanged.

Tested: the earlier head's version of this test passed 10 of 10 on an iOS 18.6 iPad Pro 13" simulator, and ConnectScreenTests passed 11 of 11. This head's CI runs the changed test.

Release notes: none