Add unit tests for Gen AI operator exception handling.

[ytoprakc]

This PR adds unit tests for exception handling for all relevant Gen AI operators as part of #61261.

• Tested: All Gen AI operators that raise explicit exceptions.
• Excluded:
  • GenAIGenerateContentOperator, GenAIGeminiListBatchJobsOperator, GenAICountTokensOperator (Handled in Add unit tests for exceptions in GCP gen. ai operators #61261 by other contributors).

[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 prek-hooks 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

[SameerMesiah97]

Looks fine (conditional on CI passing). I have left a few comments to refine the PR.

There is one general point I wanted to raise. It seems like for each test, you are asserting a different exception type. For some it's ClientError, but for others it's AirflowException or RuntimeError. If this reflects variations in the underlying semantics of the different operators, then it is perfectly fine. But if this is accidental, I would try to address this as well.

[shahar1]

It seems that you accidentally added unrelated commits to this PR - please fix.

[pierrejeambrun]

IT just needs a tiny bit adjustment to fix the CI if you don't mind.

[boring-cyborg]

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