Add a new precommit workflow to test flink container

[liferoad]

Address #33180

Will trigger this later with:

on:
  pull_request_target:
    paths:
      - 'model/**'
      - 'sdks/python/**'
      - 'release/**'
      - 'sdks/java/io/kafka/**'
      - 'runners/core-construction-java/**'
      - 'runners/core-java/**'
      - 'runners/extensions-java/**'
      - 'runners/flink/**'
      - 'runners/java-fn-execution/**'
      - 'runners/reference/**'
      - 'release/trigger_all_tests.json'
      - '.github/trigger_files/beam_PreCommit_Flink_Container.json'
  push:
    branches: ['master', 'release-*']
    tags: 'v*'
  schedule:
    - cron: '0 */6 * * *'
  workflow_dispatch:

For now, just manually trigger this for developing.

Create PreCommit Flink Container workflow

Description

This PR introduces a new PreCommit workflow to test Flink container functionality across Go, Python, and Java SDKs. The workflow runs combine load tests in each language to verify the Flink container's functionality.

Key Features

• Runs on pull requests targeting Flink-related changes
• Tests container functionality with three SDKs:
  • Go Combine test
  • Python Combine test
  • Java Combine test
• Uses self-hosted runner with Ubuntu 20.04
• Includes automatic Flink cluster setup and teardown
• Maintains consistent test parameters across languages

Implementation Details

• Triggers on:
  • PRs affecting Flink runners
  • Push to master/release branches
  • Manual workflow dispatch
• Uses Docker environments for each SDK
• Sets consistent parallelism and test parameters
• Includes proper error handling and cleanup

Notes

• Timeout set to 45 minutes for complete workflow
• Individual test steps timeout at 10 minutes
• Cluster teardown happens even if tests fail

Fixes

N/A

Related PRs

N/A

---

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.

[github-actions]

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

[github-actions]

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @Abacn for label build.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[damccorm]

Left a couple minor comments, overall LGTM though

[damccorm]

This won't work until the PR is merged

[damccorm]

I don't think we need this full condition - just github.event_name == 'pull_request_target' should be fine, often you want stuff to run on draft prs anyways.

[liferoad]

Left a couple minor comments, overall LGTM though

Let me merge this PR first since I need to do more tests and will address your comments with that PR. Thanks.