build(deps): bump github.com/mgechev/revive from 1.5.0 to 1.5.1

[dependabot[bot]]

Bumps github.com/mgechev/revive from 1.5.0 to 1.5.1.

Release notes

Sourced from github.com/mgechev/revive's releases.

v1.5.1

Changelog

• cc3ad5f7029305a998c457669d6aa488312eb311 fix #1066 by ignoring what seems legit modification of value receivers
• 1070fcdffd702e6114b7cbd885d5b044e9281a37 fix(deps): update module golang.org/x/mod to v0.22.0 (#1099)
• a4d0c434e156cac5a1f434f6172f9c1894aa0071 fix(deps): update module golang.org/x/tools to v0.27.0 (#1102)
• ce6965265a43cbfffa688a1729cab9fa907b4331 fix: cli tests on Windows; add tests-on-windows workflow
• 7ee4500e125e2d1b12653b2c8e140fec380919b4 fix: fixes #1103 by fixing the processing of max-public-structs arguments (#1114)
• c0d4d07ab65e656e02a52615ec99bdb36038db5b fix: nil panic on old go.mod (issue #1100)
• 74e2417f7d843c5581af24d353cc3e924cc6c6d6 fix: revive hangs on Windows if go.mod is not found
• 4c958ef739e982aa7108791d7afe04b76e71aa96 refactor: remove redundant defer
• be95bfa70536af6446f2b077b323923e8ccb1d09 refactor: rename files to follow Go convention
• 3378f7033b4c26c7fb987a539ddb4bad6e88b5d7 refactor: replace mutex with sync.Once for rule configuration (#1118)

Commits

• 3378f70 refactor: replace mutex with sync.Once for rule configuration (#1118)
• 7ee4500 fix: fixes #1103 by fixing the processing of max-public-structs arguments (#1...
• cc3ad5f fix #1066 by ignoring what seems legit modification of value receivers
• ce69652 fix: cli tests on Windows; add tests-on-windows workflow
• 74e2417 fix: revive hangs on Windows if go.mod is not found
• 34e9d78 docs: fix mylib example (#1121)
• 0789e36 docs: lowercase arguments for consistency
• 8c274eb docs: range-val-* rules are irrelevant for Go 1.22+
• 4c958ef refactor: remove redundant defer
• be95bfa refactor: rename files to follow Go convention
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[ti-chi-bot[bot]]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[ti-chi-bot[bot]]

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/needs-linked-issue label, please provide the linked issue number on one line in the PR body, for example: Issue Number: close #123 or Issue Number: ref #456.

_{:open_book: For more info, you can check the "Contribute Code" section in the development guide.}

---

Notice: To remove the do-not-merge/needs-tests-checked label, please finished the tests then check the finished items in description.

For example:

Tests

• [x] Unit test
• [ ] Integration test
• [ ] Manual test (add detailed scripts or steps below)
• [ ] No code

_{:open_book: For more info, you can check the "Contribute Code" section in the development guide.}

[ti-chi-bot[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 assign guo-shaoge for approval. 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](https://github.com/pingcap/tidb/blob/master/OWNERS)** 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[bot]]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[tiprow[bot]]

Hi @dependabot[bot]. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.