hub registry: migrate pingcap/tiflow images to us-docker.pkg.dev

[Copilot]

hub.pingcap.net is not cloud-accessible; all tiflow pipeline pod specs and OCI artifact host references need to move to a public-reachable registry.

Changes

• Pod YAML files (121 files): hub.pingcap.net/<image> → us-docker.pkg.dev/pingcap-testing-account/hub/<image>
  • Covers all builder images (centos7_golang-*, rocky8_golang-*, rocky9_golang-*, golang-tini:*) and utility images (network-multitool, python3-requests, mysql)
• Groovy pipeline files (119 files): OCI_ARTIFACT_HOST value migrated from hub-zot.pingcap.net/mirrors/hub → us-docker.pkg.dev/pingcap-testing-account/hub

All branches covered: latest through release-6.1 (20+ release branches).

Before:

image: hub.pingcap.net/jenkins/rocky8_golang-1.25:tini

OCI_ARTIFACT_HOST = 'hub-zot.pingcap.net/mirrors/hub'

After:

image: us-docker.pkg.dev/pingcap-testing-account/hub/jenkins/rocky8_golang-1.25:tini

OCI_ARTIFACT_HOST = 'us-docker.pkg.dev/pingcap-testing-account/hub'

Follows the same migration pattern already applied to tiflash and ticdc.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>hub registry: migrate images for pingcap/tiflow</issue_title>
<issue_description>Replace hub.pingcap.net image pulls/pushes for pingcap/tiflow with a cloud-accessible registry.

Acceptance criteria:

• No hub.pingcap.net references in jobs/pipelines for pingcap/tiflow
• Image registry endpoints documented and validated
  </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes hub registry: migrate images for pingcap/tiflow #4229

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[ti-chi-bot]

Hi @Copilot. Thanks for your PR.

I'm waiting for a PingCAP-QE member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from wuhuizuo. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• pipelines/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment