cop: ignore locks with the same start_ts (#52461)

[ti-chi-bot]

This is an automated cherry-pick of #52461

What problem does this PR solve?

Issue Number: close #52460

Problem Summary:

What changed and how does it work?

If this cop is not a stale read, which means its start_ts is fetched from PD, which means the start_ts cannot conflict with other transactions, add this ts to resolved_locks so that in a pipelined txn the locks belonging to the same txn will not block coprocessor.

For get and batch_get, they already put start_ts in resolved_locks.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below): repeating insert into t select * from t no longer reports resolve lock timeout error. I found it hard to be tested in unit test.
• 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

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (release-8.1@cfeca9b). Click here to learn what that means.
The diff coverage is 100.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-8.1     #52832   +/-   ##
================================================
  Coverage               ?   72.2701%           
================================================
  Files                  ?       1468           
  Lines                  ?     426934           
  Branches               ?          0           
================================================
  Hits                   ?     308546           
  Misses                 ?      99095           
  Partials               ?      19293           

Flag	Coverage Δ
unit	71.1408% <100.0000%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	53.9957% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	41.0929% <0.0000%> (?)

[cfzjywxk]

/merge

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cfzjywxk, you06

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [cfzjywxk,you06]

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]

@cfzjywxk: We have migrated to builtin LGTM and approve plugins for reviewing.

Please use /approve when you want approve this pull request.

The changes announcement: LGTM plugin changes

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 ti-community-infra/tichi repository.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-04-23 06:03:37.410386367 +0000 UTC m=+67374.150289279: ☑️ agreed by you06.
• 2024-04-23 07:44:49.837477811 +0000 UTC m=+73446.577380734: ☑️ agreed by cfzjywxk.