Changes

feat(prow,tekton): support CI/CD for active-active repos pingcap-inc/tidb and pingcap-inc/ticdc (#4282)

- [x] Explore repo structure and understand existing patterns
- [x] Create CI (prow jobs) for `pingcap-inc/tidb` with `release-*`
branches
- [x] Create CI (prow jobs) for `pingcap-inc/ticdc` with `release-*`
branches
- [x] Update `prow-jobs/kustomization.yaml` via
`.ci/update-prow-job-kustomization.sh`
- [x] Create new Tekton trigger binding `gcp-internal-build-params`
(internal registry without org)
- [x] Create Tekton CD trigger for `pingcap-inc/tidb` git tag create
(linux only, GCP env)
- [x] Create Tekton CD trigger for `pingcap-inc/ticdc` git tag create
(linux only, GCP env)
- [x] Update `tekton/v1/triggers/bindings/kustomization.yaml`
- [x] Update `tekton/v1/triggers/triggers/env-gcp/kustomization.yaml`
- [x] Address review feedback:
- Relaxed branch patterns to `^release-.*$` for both tidb and ticdc prow
jobs
- Changed prow job names to use `pingcap/*` prefix to reuse existing
Jenkins jobs
  - Moved Tekton triggers from `env-prod2` to `env-gcp`
- Fixed registry binding:
`us-docker.pkg.dev/pingcap-testing-account/internal` (no org)
- [x] Change ticdc prow job label `master` from `"0"` to `"1"`

<!-- START COPILOT ORIGINAL PROMPT -->



<details>

<summary>Original prompt</summary>

> 
> ----
> 
> *This section details on the original issue you should resolve*
> 
> <issue_title>Support CI/CD jobs for active-active project
repos</issue_title>
> <issue_description>## repos and branches
> - repos: `pingcap-inc/tidb`, `pingcap-inc/ticdc`
>   > it's hard forked from `pingcap/tidb` and `pingcap/ticdc`
> - branches: `release-*`
> 
> ## CI support
> - support for branch `release-*` like we did for `pingcap/tidb` and
`pingcap/ticdc` repo's release-8.5 branches.
> - do not create new Jenkins jobs, reuse the jobs as the `pingcap/tidb`
repo and `pingcap/ticdc` repo, only need to create new prow jobs to
support the new 2 repos.
> 
> ## CD support
> > here the CD flows and config defined in `tekton/v1`, we need to add
triggers and trigger template for them.
> 
> - only need to build with release profile and linux platforms for
these two repositories.
> - should use different image repositories form the new git
repositories, let's set the image repo as `*/internal/<org>/<repo>/*`
rather than `*/hub/<org>/<repo>/*`, define a trigger binding and use it
in the triggers.
> - support build for git tag create events.</issue_description>
> 
> ## Comments on the Issue (you are @copilot in this section)
> 
> <comments>
> </comments>
> 


</details>



<!-- START COPILOT CODING AGENT SUFFIX -->

- Fixes PingCAP-QE/ci#4281

<!-- START COPILOT CODING AGENT TIPS -->
---

💡 You can make Copilot smarter by setting up custom instructions,
customizing its development environment and configuring Model Context
Protocol (MCP) servers. Learn more [Copilot coding agent
tips](https://gh.io/copilot-coding-agent-tips) in the docs.

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: ti-chi-bot <71242396+ti-chi-bot@users.noreply.github.com>
Co-authored-by: wuhuizuo <2574558+wuhuizuo@users.noreply.github.com>
 (commit: 5af2ded)