[flutter_plugin_tools] Use Flutter pub for packages depending on jni

[awishere]

Packages with a jni dependency can require the Flutter SDK even when their pubspec has no direct Flutter SDK dependency. The publishing tool currently selects dart pub publish for this case, causing dependency resolution to fail for packages such as pigeon.

Recognize jni in both dependencies and dev dependencies in the shared Flutter-requirement check. This follows the narrow known-dependency approach suggested in the issue and also applies to the other pub commands using that helper. It does not attempt to resolve arbitrary transitive dependency graphs.

Fixes flutter/flutter#192709.

Validation (Dart 3.12.2, macOS arm64, from script/tool):

• The three new regression tests fail before the fix: both dependency checks return false, and the publishing test records dart pub publish instead of flutter pub publish.
• dart test — all 1,238 tests passed, including existing direct-Flutter and Dart-only behavior.
• dart analyze — no issues found.
• dart format --set-exit-if-changed . — 106 files, no changes.
• git diff --check — passed.

Publishing is exercised through the existing mocked process runner; no package was published.

Prepared with Codex assistance. This PR is a draft pending the contributor's personal review of the code and description under Flutter's AI contribution guidelines. CLA status has not yet been verified.

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.

Footnotes

1. The tool version is incremented to 0.14.4+2 and its changelog records the fix. Validation covers the complete flutter_plugin_tools test suite, not unrelated plugin suites. ↩ ↩²

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.