session: make min start ts reporter aware of internal session from get_lock() (#38790)

[ti-chi-bot]

This is an automated cherry-pick of #38790

What problem does this PR solve?

Issue Number: close #38706

Problem Summary:

Before this PR, the pessimistic transaction started by get_lock() can only live several minutes:

[WARN] [2pc.go:1118] ["stop TxnHeartBeat"] [error="txn 437065830059212803 heartbeat fail, primary key = 7480000000000000435f698000000000000001016100000000000000f8, err = txn 437065830059212803 not found"]

TiDB needs to report the minimal start ts to PD regularly, in order to advance the GC savepoint. However, the reporter is not aware of the pessimistic transaction started by get_lock(). When the GC worker cleans the lock record, the above error is reported.

What is changed and how it works?

This PR makes the min start ts reporter aware of get_lock() transaction.

Check List

Tests

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

select get_lock('hello', 0);

...
[INFO] [2pc.go:1107] ["send TxnHeartBeat"] [startTS=437068143044853763] [newTTL=31000]
...
[INFO] [2pc.go:1107] ["send TxnHeartBeat"] [startTS=437068143044853763] [newTTL=2651034]

The lock could be hold for more than 40 mins.

• No code

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.

Fix an issue that `get_lock()` cannot hold for more than 10 minutes.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

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-chi-bot]

@ti-chi-bot: This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

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/test-infra repository.

[tangenta]

6.3.x will not be released.