Add google-cloud-bigquery as explicit google-provider dependency (#38753

)

The new Google Cloud Bigquery released few days ago, caused some
weird backtracking UV issue for Python 3.11 builds where airflow uses
PyPI providers in PROD image builds. UV seems to fail on really
old version of google-cloud-bigquery (1.28.2) that has a bad version
specifier for one of the dependencies (de instead of dev).

We should add the google-cloud-bigquery explicitly and limit it to
a relatively newer version. Airflow uses latest 3.20.1 version now
in constraints and limiting bigquery to >= 3.0.1 (first non-yanked
version released > 2 years ago in March 2022) is a good lower
limit.

airflow/providers/google/provider.yaml

@@ -109,6 +109,7 @@ dependencies:
   - google-auth-httplib2>=0.0.1
   - google-cloud-aiplatform>=1.42.1
   - google-cloud-automl>=2.12.0
+  - google-cloud-bigquery>=3.0.1
   - google-cloud-bigquery-datatransfer>=3.13.0
   - google-cloud-bigtable>=2.17.0
   - google-cloud-build>=3.22.0

generated/provider_dependencies.json

@@ -529,6 +529,7 @@
       "google-cloud-automl>=2.12.0",
       "google-cloud-batch>=0.13.0",
       "google-cloud-bigquery-datatransfer>=3.13.0",
+      "google-cloud-bigquery>=3.0.1",
       "google-cloud-bigtable>=2.17.0",
       "google-cloud-build>=3.22.0",
       "google-cloud-compute>=1.10.0",