Add deferrable support for Cloud Functions invocation

[anushkagupta200615-jpg]

---

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

• Yes (please specify the tool below)

---

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

Add deferrable support for invoking and waiting on Google Cloud Functions and HTTP Cloud Run functions.

This PR introduces a production-ready operator and trigger for invoking Cloud Functions via their HTTP trigger URL, addressing the limitations of the existing CloudFunctionInvokeFunctionOperator (which uses the testing-only functions.call API).

Changes include:

• CloudFunctionInvokeTrigger: A new trigger using aiohttp to perform asynchronous, non-blocking HTTP POST requests to the Cloud Function's HTTPS trigger URL.
• CloudFunctionInvokeOperator: A new operator that natively generates OIDC ID Tokens from the Airflow gcp_conn_id credentials and makes authenticated HTTP requests to the function. It supports both synchronous execution and deferrable execution (via deferrable=True).
• Unit tests for the new trigger and operator.

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