Declare allow_driver_in_extra in the ODBC provider configuration metadata

[FrankYang0529]

Why

• Control permissibility of driver config in extra from airflow.cfg #31754 (odbc 4.0.0) added the [providers.odbc] allow_driver_in_extra option, but provider.yaml could not declare configuration at the time (that came later in Add option for storing configuration description in providers #32629), so the option was never declared in the provider metadata.
• As a result, airflow config list --section providers.odbc prints nothing and the provider has no Configuration Reference page, while airflow config get-value does return the value (ODBC Provider Configuration  #40405).

How

• Add a config: block to providers/odbc/provider.yaml.

Verification

• Unit test: uv run --no-sync pytest providers/odbc/tests/unit/odbc/hooks/test_odbc.py
• Integration test:
  • main branch

  > uv run --no-sync airflow config list --section providers.odbc
  <empty>
  > uv run --no-sync airflow config get-value providers.odbc allow_driver_in_extra
  <empty>
  > AIRFLOW__PROVIDERS_ODBC__ALLOW_DRIVER_IN_EXTRA=True AIRFLOW_HOME=$(mktemp -d) uv run --no-sync airflow config get-value providers.odbc allow_driver_in_extra
  <empty>
  

  • This branch

  > uv run --no-sync airflow config list --section providers.odbc
  [providers.odbc]
  # allow_driver_in_extra =
  > uv run --no-sync airflow config get-value providers.odbc allow_driver_in_extra
  False
  > AIRFLOW__PROVIDERS_ODBC__ALLOW_DRIVER_IN_EXTRA=True AIRFLOW_HOME=$(mktemp -d) uv run --no-sync airflow config get-value providers.odbc allow_driver_in_extra
  True
  

---

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

• Yes - Claude Code

---

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