*: Log SQL statement when coprocessor encounteres lock (#27735)

[ti-srebot]

cherry-pick #27735 to release-4.0
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/27926

After apply modifications, you can push your change to this PR via:

git push [email protected]:ti-srebot/tidb.git pr/27926:release-4.0-649ed6abc979

---

What problem does this PR solve?

Issue Number: close #27718

Problem Summary: The debug log on coprocessor encounters lock doesn't print out the statement, which makes it difficult to know what statement was affected by the lock. This PR tries to add the log.

What is changed and how it works?

What's Changed: Added a callback parameter to the Send method of kv.Client that accepts a new TransactionEvent object. This avoids to pass the SQL statement deep down to the coprocessor client part. And I think this callback and events can also be reused by Lock View.

How it Works:

Check List

Tests

• Manual test (add detailed scripts or steps below) (TODO)

Side effects

• Performance regression: Consumes more CPU

Documentation

• None

Release note

None.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• cfzjywxk
• sticnarf

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-srebot]

/run-all-tests

[ti-srebot]

@MyonKeminta you're already a collaborator in bot's repo.

[cfzjywxk]

@MyonKeminta
Do we need to pick to v4.0.x ?

[MyonKeminta]

@MyonKeminta
Do we need to pick to v4.0.x ?

I'm asked to do so. But I'll hold it until these PRs are confirmed can be merged in these release branches, since it's quite annoying to resolve the conflicts.

[tiancaiamao]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: b8ba4f9

[tiancaiamao]

/merge