feat(pipelines/pingcap/tidb/latest): enable coverage upload in job

[Defined2014]

ref pingcap/tidb#45930

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.
The pull request is adding a new feature to the existing codebase. It enables coverage upload in the job and uses the prow.uploadCoverageToCodecov function to upload the coverage data to Codecov. The new code is added in the stage("Checks") and post sections.

Potential problems:

• It is not clear from the pull request description why this feature is needed or what problem it solves.
• The pull request lacks any tests to show that the new feature is working as expected.
• It is also unclear whether the necessary authentication is in place to upload coverage data to Codecov, and whether this authentication is secure.

Fixing suggestions:

• The pull request should have a more detailed description to explain the need for the new feature, how it works, and how it benefits the project.
• The pull request should include tests for the new feature to ensure that it is working as expected.
• The authentication used to upload coverage data to Codecov should be secure, and the pull request should include documentation on how to set up and use this authentication.

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.
The pull request adds a new feature to the pipeline for the PingCAP TiDB project, which enables coverage upload in the job. Specifically, it adds an environment variable for the CODECOV_TOKEN and a new post-build step to upload coverage data to Codecov.

One potential problem is that the CODECOV_TOKEN is hardcoded in the script, which could lead to security vulnerabilities if the token is exposed. It might be better to use a secret management tool like Vault or store the token in an environment variable outside of the script.

Another suggestion would be to add some tests for the new feature to ensure that it works as expected and does not introduce any regressions.

Overall, the pull request looks good, but the potential security issue and lack of tests should be addressed before merging.

[wuhuizuo]

/hold

It's need to test.

[wuhuizuo]

/lgtm
/approve

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-08-09 07:28:00.660409664 +0000 UTC m=+97645.209425646: ☑️ agreed by wuhuizuo.

[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:

• pipelines/OWNERS [wuhuizuo]

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

[wuhuizuo]

testing in: https://do.pingcap.net/jenkins/job/pingcap/job/tidb/job/ghpr_mysql_test/26772/

[wuhuizuo]

/unhold

it's passed.

[wuhuizuo]

Ref: #2171