[pigeon] Pin ffigen and jnigen to fix the tree

[QuncCccccc]

Fixes the red tree on main (Mac_arm64 custom_package_tests master/stable, Linux_android custom_package_tests master), which is also blocking the flutter→packages roll (#13091).

No change in this repo caused it: d5ec6dbaf1 was green and the next commit (249ddc0d0b, docs-only) was red. The breakage started with the first CI run after dart-lang/native published new versions of pigeon's dev_dependencies (~02:51 UTC 2026-10-01, via dart-lang/native#3716):

• ffigen 22.1.0 removed defaultCompilerOpts from its public API, but the latest swiftgen (0.2.0) still calls it, so FFIgen generation fails on macOS:
  swiftgen-0.2.0/lib/src/generator.dart:101:17: Error: Method not found: 'defaultCompilerOpts'.
  (build)
• jnigen 1.0.1 changes the generated header and JniVersionCheck(1, 0) → (1, 1), so the checked-in native_interop_tests.gen.jni.dart no longer matches generator output on Linux.
  (build)

This pins both (ffigen ">=22.0.0 <22.1.0", jnigen ">=1.0.0 <1.0.1") in the four pigeon pubspecs that depend on them, with TODOs to remove the pins once upstream is fixed. These are all dev_dependencies, so there is no impact on pigeon clients; the top-level pubspec.yaml change isn't auto-exempted by the repo tool, so this needs override: no versioning needed and override: no changelog needed.

Verified locally:

• With the pin, swiftgen + the test plugin's ffigen config compile; with ffigen 22.1.0 the same compile fails with the CI error above.
• The checked-in JNI bindings were generated by jnigen 1.0.0, which is what the pin resolves to (same as the last green run).

Upstream issue: dart-lang/native#3723

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩²

[gemini-code-assist]

Code Review

This pull request adds upper bound constraints to the ffigen and jnigen dev_dependencies across multiple pubspec.yaml files in the pigeon package, its examples, and platform tests. Specifically, ffigen is restricted to '>=22.0.0 <22.1.0' and jnigen is restricted to '>=1.0.0 <1.0.1' to address compatibility issues with swiftgen. There are no review comments, and I have no feedback to provide.

[QuncCccccc]

Talked with @tarrinneal offline and a fix with some other changes will be ready is in #13103. So I'm closing this one:)!