Set minimum dependencies for apache-beam deps on Py 3.12+3.13

[ashb]

Set minimum dependencies for apache-beam on Py 3.12+3.13

Older versions of apache-beam package depend upon gprcio-tools, but the
version requirement they specify doesn't work on Py 3.12, but the metadata
doesn't say that, so it tries to compile it and fails.

---

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

[potiuk]

Cool !

[amoghrajesh]

Looks like it will work, aligning with the last fix for beam

[ashb]

Odd, that didn't seem to work:

  + uv pip install --python /usr/local/bin/python --resolution lowest-direct --upgrade --editable '.[apache-beam]' --editable ./task_sdk
  Using Python 3.12.8 environment at: /usr/local
  Resolved 179 packages in 4.73s
    × Failed to download and build `apache-beam==2.55.0`
    ├─▶ Failed to install requirements from `build-system.requires`
    ├─▶ Failed to build `grpcio-tools==1.53.0`

[ashb]

I'm going to set the min version of apache-beam itself instead.

[potiuk]

Ah. This is because apache-beam 2.55.0 has grpcio.tools as "build requirements" not "requirements". In a modern build packaging - when a frontend is building package (because it does not have corresponding binary wheel) it will perform the build of that package from .sdist in "isolated build environment" -> where it downloads and sets up temporary venv with the dependencies specified in the "build requirements" of that package.

From the error looks like apache-beam 2.55.0 has grpcio-tools 1.53.0 set as their build requirements.

[potiuk]

So yeah - we should limit apache.beam not grpc-tools in this case.