ci(ios): add ensure-simulator-ready script for reliable boot/ready waits

[mikehardy]

Description

I've just finished doing a large amount of e2e de-flaking in the related react-native-firebase repository, and Simulator boots were a large source of problems - I know FlutterFire has suffered from the same issues, and FutterFire appears to be on macOS 15 still, as that changes to macOS26 and Xcode 26 the problem intensifies

This is a port of the more robust boot-status polling from react-native-firebase CI: wait for simctl bootstatus after simulator-action (or simctl boot) - I've seen good results even on macOS 26 / Xcode 26.5 / iPhone 17 with this, where previously it was unusable.

Related Issues

Unknown if there are CI flake umbrella issues but this would apply

• react-native-firebase related - test: fix coverage for typescript, java, and add iOS native + fix 3 e2e flake failure modes invertase/react-native-firebase#9054 (the commits are contained in that commit stream)

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (melos run analyze) does not report any problems on my PR.
• I read and followed the Flutter Style Guide.
• I signed the CLA.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change.
• No, this is not a breaking change.

[gemini-code-assist]

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.