ci: update the tag used for kubetest2

[csuzhangxc]

What problem does this PR solve?

before this PR (with git describe tags):

[2024-10-16T08:02:06.235Z] CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go test -cover -covermode=atomic -coverpkg=$(go list ./cmd/... ./pkg/...  github.com/pingcap/tidb-operator/pkg/apis/...  github.com/pingcap/tidb-operator/pkg/client/... | grep -vE "pkg/client" | grep -vE "pkg/apis/pingcap" | sed 's|github.com/pingcap/tidb-operator/|./|' | tr '\n' ',') -ldflags 'GIT_VERSION should be a valid Semantic Version. Current value: kubetest2-v0.1.0.3+a01a11a14cbaf7-dirty Please see more details here: https://semver.org/' -c -o images/tidb-operator/bin/tidb-controller-manager ./cmd/controller-manager

[2024-10-16T08:02:07.159Z] invalid value "GIT_VERSION should be a valid Semantic Version. Current value: kubetest2-v0.1.0.3+a01a11a14cbaf7-dirty Please see more details here: https://semver.org/" for flag -ldflags: missing =<value> in <pattern>=<value>

[2024-10-16T08:02:07.159Z] usage: go test [build/test flags] [packages] [build/test flags & test binary flags]

What is changed and how does it work?

Code changes

• Has Go code change
• Has CI related scripts change

Tests

• Unit test
• E2E test
• Manual test
• No code

Side effects

• Breaking backward compatibility
• Other side effects:

Related changes

• Need to cherry-pick to the release branch
• Need to update the documentation

Release Notes

Please refer to Release Notes Language Style Guide before writing the release note.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from csuzhangxc, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[csuzhangxc]

/cherry-pick release-1.6

[ti-chi-bot]

@csuzhangxc: once the present PR merges, I will cherry-pick it on top of release-1.6 in the new PR and assign it to you.

In response to this:

/cherry-pick release-1.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[csuzhangxc]

/cherry-pick release-1.5

[ti-chi-bot]

@csuzhangxc: once the present PR merges, I will cherry-pick it on top of release-1.5 in the new PR and assign it to you.

In response to this:

/cherry-pick release-1.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

@csuzhangxc: new pull request created to branch release-1.6: #5770.

In response to this:

/cherry-pick release-1.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

@csuzhangxc: new pull request created to branch release-1.5: #5771.

In response to this:

/cherry-pick release-1.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.