*: fix bug that write on temporary table send request to TiKV

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #xxx

Problem Summary:

Write on a temporary table should not send request to TiKV

What is changed and how it works?

What's Changed:

Fix a bug introduced by #24196
I thought remove the temporary KV entries from the transaction buffer could avoid sending request to TiKV.
But I'm wrong. The membuffer.Delete() API causes sending delete keys to TiKV ...

How it Works:

Now I use the transaction SetKVFilter() API to ignore the temporary table KV entries.
See https://github.com/tikv/client-go/blob/b9e4cb538f3028c8a3cdaa6d04d6b47e2dcb322c/tikv/2pc.go#L357

Check List

Tests

• Unit test

Release note

• No release note

[djshow832]

Can you test it manually, on a real cluster?

[tiancaiamao]

Can you test it manually, on a real cluster?

Yes, it's when I testing the feature manually that I found this bug. @djshow832

The test case is now changed to cover writing without network (you can check the failpoint).

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• coocood
• djshow832

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.

[tiancaiamao]

/merge

[ti-chi-bot]

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

Commit hash: 0dd1714

[zhouqiang-cl]

/run-unit-test

[ti-srebot]

cherry pick to release-5.0 in PR #26516

[ti-srebot]

cherry pick to release-5.1 in PR #26519