feat(tidb): add ddlv1 unit test pipeline

[purelind]

This pull request introduces a new Jenkins pipeline job for running unit tests on the latest version of the pingcap/tidb repository. It includes the creation of the pipeline job, its definition, and updates to the relevant presubmits configuration.

New Jenkins Pipeline Job:

• jobs/pingcap/tidb/latest/pull_unit_test_ddlv1.groovy: Added a new pipeline job definition for pingcap/tidb/pull_unit_test_ddlv1, including parameters, properties, and SCM configuration.
• pipelines/pingcap/tidb/latest/pull_unit_test_ddlv1.groovy: Implemented the pipeline script for the new job, setting up Kubernetes agents, environment variables, and stages for debugging, checkout, and testing.

Presubmits Configuration:

• prow-jobs/pingcap/tidb/latest-presubmits.yaml: Added a new presubmit configuration for the pingcap/tidb/pull_unit_test_ddlv1 job, including branches, trigger commands, and context settings.Add a new pipeline foro ddlv1 unit test, we need to monitor the stability of the new pipeline, only support trigger manually currently.

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.

Summary of changes:

• A new pipeline for ddlv1 unit test has been added for the pingcap/tidb repository.
• The pipeline can only be triggered manually.
• The pull_unit_test_ddlv1.groovy and pod-ghpr_unit_test.yaml files have been added to the repository.
• A new entry for the pull_unit_test_ddlv1 job has been added to the latest-presubmits.yaml file.

Potential problems:

• The pipeline can only be triggered manually. It would be better if it could be triggered automatically when there is a change in the codebase.
• It is unclear what the PROW_JOB_ID parameter is used for. It should be documented or removed if it is not needed.
• The retry function is used in the Checkout stage without specifying the maximum number of retries. It would be better to set a limit to avoid infinite retries.

Suggestions for fixes:

• Add an automatic trigger to the pipeline whenever there is a change in the codebase.
• Document the purpose of the PROW_JOB_ID parameter or remove it if it is not needed.
• Set a maximum number of retries for the retry function in the Checkout stage.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wuhuizuo

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

The pull request process is described here

Needs approval from an approver in each of these files:

• jobs/OWNERS [wuhuizuo]
• pipelines/OWNERS [wuhuizuo]
• prow-jobs/OWNERS [wuhuizuo]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-09-30 06:28:01.350615119 +0000 UTC m=+249836.770828127: ☑️ agreed by wuhuizuo.