Bump lower-limit for pinotdb (#37690)

The pintodb python package had a very old and very low lower
limit, that introduced possible weird resolutions for dependencies
when pinotdb had been downgraded to **really** low version - this
has been observed in #37683 when we test replacing pip with uv
in our CI environment.

Bumping it to version >= 5.1.0 released last year in september - that
was the first one that was not 0.N.*.

airflow/providers/apache/pinot/provider.yaml

@@ -49,7 +49,7 @@ versions:
 dependencies:
   - apache-airflow>=2.6.0
   - apache-airflow-providers-common-sql>=1.3.1
-  - pinotdb>0.4.7
+  - pinotdb>=5.1.0
 
 integrations:
   - integration-name: Apache Pinot

generated/provider_dependencies.json

@@ -223,7 +223,7 @@
     "deps": [
       "apache-airflow-providers-common-sql>=1.3.1",
       "apache-airflow>=2.6.0",
-      "pinotdb>0.4.7"
+      "pinotdb>=5.1.0"
     ],
     "devel-deps": [],
     "cross-providers-deps": [

pyproject.toml

@@ -613,7 +613,7 @@ apache-livy = [ # source: airflow/providers/apache/livy/provider.yaml
 apache-pig = [] # source: airflow/providers/apache/pig/provider.yaml
 apache-pinot = [ # source: airflow/providers/apache/pinot/provider.yaml
   "apache-airflow[common_sql]",
-  "pinotdb>0.4.7",
+  "pinotdb>=5.1.0",
 ]
 apache-spark = [ # source: airflow/providers/apache/spark/provider.yaml
   "grpcio-status>=1.59.0",