fix(ci): align Android toolchain and analyzer with Flutter 3.47

[SelaseKay]

Description

Unpinned Flutter 3.47.0 on CI raised the Android dependency floors and enabled unawaited_return_in_try_block, which is currently failing main independently of feature PRs (format, analyze, android-unit-tests, agp9-compatibility).

• Bump the aggregate tests/android app to Gradle 8.14, AGP 8.11.1, and Kotlin 2.2.20 (Flutter 3.47 error thresholds).
• return await Pigeon HostApi calls in async try blocks in firebase_analytics_platform_interface.
• Add the native-dir analyzer.exclude entries that Flutter 3.47's analysis_options.yaml migrator writes (build/**, android/**, ios/**, web/**, windows/**, macos/**, linux/**) to each analysis_options.yaml it will open. The 3.47 migrator does not follow include:, so putting the list only on the repo root is not enough to keep format CI from rewriting nested files.
• dart-format the one pipeline e2e test CI rewrote.
• Temporarily pin the Firestore web-wasm e2e job to Flutter 3.44.0 (JS web stays on unpinned stable) to check whether the dart2wasm TFA startAfter failure is 3.47-specific.

Related Issues

None

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.