planner: fix the issue of reusing wrong point-plan for "select ... for update" (#54661)

[qw4990]

This is an automated cherry-pick of #54661

What problem does this PR solve?

Issue Number: close #54652

Problem Summary: planner: fix the issue of reusing wrong point-plan for "select ... for update"

What changed and how does it work?

Encode more txn state into the plan cache key, and check whether the key has changed before reusing point-get plans.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[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 qw4990 and additionally assign bb7133, benjamin2037, easonn7, gmhdbjd, leavrth, tangenta, windtalker, yudongusa, zimulala for approval(Please 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
• br/OWNERS
• br/pkg/storage/OWNERS
• lightning/OWNERS
• pkg/autoid_service/OWNERS
• pkg/bindinfo/OWNERS
• pkg/config/OWNERS
• pkg/ddl/OWNERS
• pkg/distsql/OWNERS
• pkg/disttask/OWNERS
• pkg/domain/OWNERS
• pkg/executor/importer/OWNERS
• pkg/expression/OWNERS
• pkg/infoschema/OWNERS
• pkg/lightning/OWNERS
• pkg/meta/OWNERS
• pkg/owner/OWNERS
• pkg/parser/OWNERS
• pkg/planner/OWNERS
• pkg/session/OWNERS
• pkg/sessionctx/variable/OWNERS
• pkg/statistics/OWNERS
• pkg/table/OWNERS
• pkg/tablecodec/OWNERS

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

[tiprow]

Hi @qw4990. 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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.