Run python_dependency_tests during release validation.

[tvalentyn]

Python beam 2.72.0 containers fail pip check.

docker run --rm -it --entrypoint=/bin/bash apache/beam_python3.11_sdk:2.72.0
root@dba2986b7302:/# pip check
apache-beam 2.72.0 requires pillow, which is not installed.

The rootcause:

• pillow was was added in https://github.com/apache/beam/pull/37735/changes due to merge conflict (adding it was the right thing to do, but we overlooked that deps were not regenerated).
• The test suite that verified dependencies failed in
  https://github.com/apache/beam/actions/runs/22566799492/job/65364608931 but went unnoticed because at that time we were merging on red and tests were a mess.
• The test suite that can catch this is not part of the release suite - as far as I can tell, it didn't run on [DO NOT MERGE] Run all PostCommit and PreCommit Tests against Release Branch #37839, hence this PR.

I have the following asks that should help reduce preventable issues in the release :

• We should take a look whether any other tests suites need to be amended to also run during release branch validation.
• We need to change the release procedure to rerun tests on the release validation PR after making cherry-pick changes. If we only run the tests once, we might miss errors like this.
• We should investigate errors on the test suite validation PR before proceeding with the release: [DO NOT MERGE] Run all PostCommit and PreCommit Tests against Release Branch #37839 (comment)

Thanks!

cc: @Amar3tto @damccorm @Abacn @claudevdm

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[tvalentyn]

R: @Amar3tto

[github-actions]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

[tvalentyn]

We should take a look whether any other tests suites need to be amended to also run during release branch validation.

@Amar3tto Would you have bandwidth to help with this? Thanks!

Also wondering if trigger_all_tests.json should be a part of the github repo like other trigger files we have.

[Abacn]

We should take a look whether any other tests suites need to be amended to also run during release branch validation.

There is a check enforcing all beam_PreCommit and beam_PostCommit to have this trigger file:

beam/.github/build.gradle

Line 54 in 5932587

if (paths != null && !paths.contains('release/trigger_all_tests.json') && !fname.toLowerCase().contains('sickbay') && !workflow.name.toLowerCase().contains('disabled')) {

but this specific test did not follow these naming convention