UI: Hide run-on-latest-version option for non-versioned bundles

[WonYong-Jang]

Context

Non-versioned bundles (e.g. LocalDagBundle) always leave the run's bundle_version null and resolve to the latest serialized Dag at run time, so the "run on latest bundle version" checkbox was a no-op there while still being shown. Toggling it produced no effect, which eroded trust in the control.

The visibility is now gated on the run being pinned to a bundle version that actually differs from the latest - the case where it changes the outcome.
The clear-run, clear-task-instance, and clear-group dialogs share the same getRunOnLatestVersionState helper, so all three are fixed consistently.

closes: #70371

Verification

clearing a LocalDagBundle run whose Dag version differs from the latest: the "run on latest bundle version" checkbox is now hidden.

---

Was generative AI tooling used to co-author this PR?

• Yes - Claude Code (Opus 4.8)

Generated-by: Claude Code (Opus 4.8) following the guidelines

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example Dag that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack