feat(pingcap/tidb-tools): add integration tests

[purelind]

add integration tests

[ti-chi-bot[bot]]

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

This pull request adds integration tests to the pingcap/tidb-tools pipeline. The changes include adding a new stage for Integration Test, downloading and extracting artifacts, and running integration tests. The integration tests include checking if the required binaries are present, testing MySQL connection, and running the integration tests.

Some potential problems that could arise from this pull request include:

• The integration test stage is missing a dependency check to ensure that the necessary files are present before running the tests.
• The make integration_test command does not have any arguments to specify which tests to run, which could lead to running all tests instead of just the necessary ones.
• The post-build section archives artifacts and prints the logs, but it does not specify where to store these logs, which could lead to confusion in case of multiple builds.

To fix these issues, I suggest the following:

• Add a dependency check before running the integration tests to ensure that all necessary files are present.
• Add arguments to the make integration_test command to specify which tests to run.
• Specify the location to store the archived artifacts and logs in the post-build section.

[purelind]

test on https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Ftidb-tools%2Fpull_verify/detail/pull_verify/12/pipeline/

[ti-chi-bot[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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/pingcap/tidb-tools/OWNERS](https://github.com/PingCAP-QE/ci/blob/main/pipelines/pingcap/tidb-tools/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment