Add ability to provide proxy for dbt Cloud connection

[b-per]

Adding the ability to define proxy settings when connecting to dbt Cloud. This can be useful for people setting up IP restrictions on dbt Cloud, allowing only some IPs to connect.

This is my first contribution to Airflow, so feel free to let me know if I need to do anything else.

I update the code for the hooks and added some documentation.

I didn't add tests as I am not too sure of how I could do it in that case, but I am happy to do so with a bit of pointers/guidance.

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[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 (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits 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

[potiuk]

Needs unit tests.

[b-per]

Happy to add some, but I am not able run the existing ones. Hence why I was wondering if there was any pointer or guidance.

If I do a pytest tests/providers/dbt/cloud/ in my hatch env I get a ModuleNotFoundError: No module named 'sqlalchemy' but sqlalchemy is indeed installed

[b-per]

I actually managed to run the tests with breeze testing tests --test-type "Providers[dbt.cloud]".

I have updated them so that they pass again and I have added an extra test with the proxy.

Let me know if instead of creating a new test you prefer if I update all the pytest.mark.parametrize to include the connection with a proxy.

My rationale for adding a new test for the proxy rather than as a parameter for all tests is that most people using the providers won't need the proxy.

[potiuk]

If I do a pytest tests/providers/dbt/cloud/ in my hatch env I get a ModuleNotFoundError: No module named 'sqlalchemy' but sqlalchemy is indeed installed

BTW. Re venv - you should be able to run the test in venv created with `pip install -e ".[dbt.cloud,devel-tests]" - that should install all what is needed to run the tests.

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.