[infra] add runTarget

[pq]

Adds a parameterized runTarget Gradle task letting us run and test the plugin against multiple IDE targets (IntelliJ IDEA Community, Ultimate, and Android Studio) without changing the primary compilation classpath.

This is modeled after the approach taken in flutter-intellij PR #8910 with a few tweaks.

Key Bits

• Centralized IDE Version: Extracts the hardcoded IDE version to gradle.properties as ideaVersion.
• Parameterized runTarget Task: Registered a custom runTarget task using the intellijPlatformTesting extension that accepts -Pide and -PideV parameters.
• Self-Documenting CLI: Running ./gradlew runTarget without parameters displays usage instructions and stops execution.
• Enhanced printProductsReleases: Updates the task to include Android Studio releases and provided instructions for mapping the output to task parameters.

Differences from flutter-intellij/pull/8910

• Fallback Version Adjustment: For the default fallback (when no parameters are provided), we use IntelliJ Community "2024.2" instead of the project's compilation target "2025.3.1.1". This avoids resolution errors caused by JetBrains changing the publication structure for Community editions starting with version 2025.3. (Note this is just for printing the help docs and not for actually running anything.)
• Local IDE Path Support (-PidePath): We added a new parameter -PidePath to allow running against a local IDE installation (e.g., ./gradlew runTarget -PidePath=/Applications/Android\ Studio.app). This was added to bypass brittle automated resolution issues specifically associated with Android Studio releases in the new Gradle plugin.

Fixes: #316

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our [contributor guide](https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Dart contributions to our repos should follow the Dart style guide and use dart format.
• Java and Kotlin contributions should strive to follow Java and Kotlin best practices (discussion).

[gemini-code-assist]

Code Review

This pull request externalizes the IntelliJ IDEA version to gradle.properties and introduces a new runTarget task to facilitate launching various IDE types (Community, Ultimate, Android Studio) or local installations via command-line properties. The printProductsReleases task was also enhanced to support more channels and types. Feedback includes suggestions to document the hardcoded fallback version, reduce property fetching duplication, and replace println calls with the idiomatic Gradle logger.lifecycle to comply with the project's logging standards.