Move type-only third-party imports under TYPE_CHECKING in providers

[omkar-334]

Third-party names that are only used in type annotations. Every file in this PR already has from __future__ import annotations, so those annotations are stored as strings at runtime. The imports never need to be in sys.modules to make the code work; they only need to be resolvable for static analysis. No runtime imports were moved inline

Related issue - #67515, #67519 (comment)

Each change is the same shape:

-from third_party import RuntimeName, TypeOnlyName
+from third_party import RuntimeName

 if TYPE_CHECKING:
+    from third_party import TypeOnlyName

How candidates were picked

A small AST pass over providers/*/src flagged top-level third-party imports whose every reference falls in an annotation position (function args, returns, AnnAssign).

---

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

• Yes
  Generated-by: Claude Code, following the guidelines

[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

[kaxil]

No, not this of a change. What I meant is move imports where the module hasn't already been imported.

In this case alibabacloud_adb20211201.models is already imported on L26, so this change won't have any impact