fix: pass through user-provided password in HiveServer2Hook for all auth modes

[YoannAbriel]

Problem

HiveServer2Hook.get_conn() silently drops user-provided passwords when auth_mechanism is anything other than LDAP, CUSTOM, or PLAIN. When auth_mechanism defaults to NONE (the most common case), the password is never passed to pyhive.hive.connect(), which then defaults to sending "x" as the password on the wire. Users see their configured password ignored regardless of what they set in the connection form.

Root Cause

The password assignment in get_conn() was gated behind if auth_mechanism in ("LDAP", "CUSTOM", "PLAIN"). For any other auth mode, password stayed None even when db.password was explicitly set by the user.

Fix

Changed the condition to if db.password: so the user-provided password is always passed through to pyhive when set, regardless of the auth mechanism. Added a test verifying password pass-through with the default NONE auth mechanism.

Closes: #62338

---

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

• Yes — Claude Code

Generated-by: Claude Code 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 or {issue_number}.significant.rst, in airflow-core/newsfragments.

[eladkal]

wasn't this already fixed by #62364 ?

[YoannAbriel]

Thanks for flagging! #62364 only added PLAIN to the list of mechanisms that retrieve the password. This PR takes a different approach — it ensures the user-provided password is passed through for all auth modes (NOSASL, NONE, KERBEROS, LDAP, CUSTOM, etc.) instead of maintaining a growing allowlist. The fix in #62364 still leaves other mechanisms unable to use a configured password.