Changes

TiCDC: Update Prow jobs to use dedicated build and test pod templates and enable 'all' trigger. (#3836)

This PR introduces a new pod template file (`pod-build.yaml`) for
build-related jobs and renames the existing test pod template file to
`pod-test.yaml`. This change aims to provide better resource allocation
and configuration separation between build and test environments.

The following changes have been made:

* Introduced `pod-build.yaml` with specific resource allocations for
build containers.
* Renamed existing `pod.yaml` files to `pod-test.yaml` for clarity in
integration test jobs.
* Updated pipeline groovy files to reference the new `pod-build.yaml`
for build stages and the renamed `pod-test.yaml` for test stages.
* Updated Prow job configurations to include the `all` keyword in the
trigger for various jobs, allowing them to be run with a single `/test
all` command.
* Increased CPU allocation for the `golang` container in
`pull_cdc_pulsar_integration_light_next_gen/pod.yaml` from 6 to 12 cores
to accommodate build needs.
* Removed the `utils` container from the test pod templates
(`pod-test.yaml`) as it is now included in the `pod-build.yaml` for
build stages.
* Added `run_before_merge: true` to `pull-unit-test-next-gen` and
`pull-build-next-gen` jobs in `latest-presubmits-next-gen.yaml`.
* Added `all` to the trigger for several integration test jobs in
`latest-presubmits-next-gen.yaml`.

---------

Signed-off-by: tenfyzhong <tenfy@tenfy.cn>
 (commit: f827947)