[yuseok89]

Airflow 3 reads connection form metadata from provider.yaml and ignores the deprecated hook methods when the YAML is present, so hook-side edits were silently not reaching the UI. A full scan across all providers found the drift below, presumably from the metadata living in two places, no static check covering ui-field-behaviour, and the habit of editing the hook. A follow-up will extend the static check.

Provider	Connection type	Change
airbyte	airbyte	YAML catches up, login/password relabels gain "(optional)"
alibaba	alibaba_cloud	Remove a get_ui_field_behaviour() override that only called super()
apache.arrow	adbc	Add missing hook-name and ui-field-behaviour
arangodb	arangodb	Hook fix, double space in the host relabel
common.ai	pydanticai	YAML catches up, extra placeholder and Ollama host hint; hook fix, double space
common.ai	pydanticai-azure	YAML catches up, extra placeholder
common.ai	pydanticai-bedrock	YAML catches up, extra placeholder
common.ai	pydanticai-vertex	YAML catches up, extra placeholder
common.ai	langchain	YAML catches up, extra placeholder
git	git	YAML catches up, eight missing keys in the extra placeholder
google	leveldb	Add missing conn-fields and ui-field-behaviour
microsoft.azure	azure	YAML catches up, cloud_environment placeholder
microsoft.azure	azure_service_bus	Hook fix, "authenticaltion" typo; YAML fix, stray space in the connection string placeholder
snowflake	snowflake	YAML catches up, WORKLOAD_IDENTITY authenticator and workload_identity_provider placeholder
telegram	telegram	Hook fix, extra listed twice in hidden_fields

JSON-formatting-only differences (aws, emr, athena, ibmmq, teradata, trino) are left as-is. get_provider_info.py files are regenerated by prek.

---

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

• Yes (please specify the tool below)
  • Fable 5

---

• 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.

[amoghrajesh]

Thanks, CI needs fixing.

[yuseok89]

Thanks for the review.
CI was green when I first checked, but the static checks failure after marking this ready for review turned out to be unrelated to this PR.
Rebased onto latest main to pick up the fix.