[GitHub Actions] Self-hosted runners migration

[dannymartinm]

DO NOT MERGE

As part of the issue 21106, @elink21 and I have implemented the self-hosted runners for the Ubuntu and Windows operating systems.

In this PR you will find the following changes:

• Updates in workflows to runs-on self-hosted runners (Ubuntu and Windows)
• Docker and Kubernetes files to reproduce the environment of the Ubuntu runners in local and in Google Kubernetes Engine
• Scripts for the Windows runners implementation on GCP Compute Engine (VMs)
• Cloud Function scripts
• Detailed documentation in README files

Note: We will rely on GitHub-hosted runners for MacOS builds until a straightforward implementation approach comes out.

PR#16511 : Previous PR for reference.
BEAM-12812: Original Jira may contain additional context.

Migration Release Plan
Once this PR is approved, we are planning to create one PR per workflow and merge one by one in case some rollback is needed.

Thank you very much!

---

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

• Choose reviewer(s) and mention them in a comment (R: @username).
• 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.

[elink21]

Status update: reviewed by @damccorm, waiting for the migration window to deploy the infrastructure and request the merge.

[damccorm]

@dannymartinm @elink21 what should we do with this PR at this point? The docs are probably still helpful to have, but the workflow changes have been pushed out into separate PRs

[elink21]

@dannymartinm @elink21 what should we do with this PR at this point? The docs are probably still helpful to have, but the workflow changes have been pushed out into separate PRs

Fortunately documentation was also divided into individual PRs, however due to the latest changes I will work on updating the infrastructure specs and it's documentation, if I'm not wrong this PR with all the changes was created as a reference for a quicker review, but everything was included in the other ones. For me it looks like we can close this one, what do you think @dannymartinm ?

[dannymartinm]

@dannymartinm @elink21 what should we do with this PR at this point? The docs are probably still helpful to have, but the workflow changes have been pushed out into separate PRs

Fortunately documentation was also divided into individual PRs, however due to the latest changes I will work on updating the infrastructure specs and it's documentation, if I'm not wrong this PR with all the changes was created as a reference for a quicker review, but everything was included in the other ones. For me it looks like we can close this one, what do you think @dannymartinm ?

Hi @elink21 and @damccorm , yes this PR was a previous step for the release and merging process just to have the full picture of our changes. We have split this PR into small ones (some of them already merged).

We can close this PR. Thank you team!