Migrate connection UI metadata to YAML for some providers

[amoghrajesh]

---

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

• Yes: Cursor IDE

Follow up to: #60410

Starting this effort with important candidates:

1. Google
2. Microsoft
3. Amazon
4. Vault
5. Databricks
6. Snowflake

Generated some prompts that run the helper script: https://github.com/astronomer/airflow/blob/9a69169629b81bae43868788b52f640c57f533ba/contributing-docs/23_provider_hook_migration_to_yaml.rst for these one by one and run some validations for it too.

---

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

[potiuk]

nice!

[choo121600]

Cool 🙌

[amoghrajesh]

Let me run it with full tests too

[amoghrajesh]

Okay finally we are green here.

[github-actions]

Backport successfully created: v3-1-test

            Note: As of [Merging PRs targeted for Airflow 3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
            the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

            In matter of doubt please ask in [#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) Slack channel.

                <tr>
                <th>Status</th>
                <th>Branch</th>
                <th>Result</th>
            </tr>
            <tr>
                <td>✅</td>
                <td>v3-1-test</td>
                <td><a href="https://github.com/apache/airflow/pull/62075"><img src="https://img.shields.io/badge/PR-62075-blue" alt="PR Link"></a></td>
            </tr>
        </table>