executor: change pessimistic lock wait start for one statement

[cfzjywxk]

What problem does this PR solve?

When retry is needed, like write conflict or single statement rollback for pessimistic transactions, the Pessimistic transaction lock wait start time will be reset to time.Now() in ActionPessimisitcLock.HandleBatch.

What is changed and how it works?

Add one field in stmtCtx recording the pessimistic lock wait start time, and reuse this value when doing retry

Check List

Tests

• Manual test (add detailed scripts or steps below)

1. Change innodb_lock_wait_timeout to 10 seconds
2. Start a pessimistic transaction in one session
3. Start an optimistic transaction which will conflict with that in 2
4. Start another pessimistic transaction in another session, try to lock the same key
5. After 2 and 4 both retry work done, one will got the pessimistic lock, the other one timed out but not wait another 10 seconds

Code changes

• Has exported function/method change
• Has exported variable/fields change
• Has interface methods change

Side effects

• Increased code complexity

Related changes

• Need to cherry-pick to the release branch

Release note

[codecov]

Codecov Report

Merging #13922 into master will decrease coverage by 0.1271%.
The diff coverage is 77.2727%.

@@               Coverage Diff                @@
##             master     #13922        +/-   ##
================================================
- Coverage   80.2726%   80.1454%   -0.1272%     
================================================
  Files           480        480                
  Lines        120898     120043       -855     
================================================
- Hits          97048      96209       -839     
- Misses        16143      16151         +8     
+ Partials       7707       7683        -24

[jackysp]

LGTM

[lysu]

LGTM, can we add a test case via failpoint to return WriteConflictError once?

[cfzjywxk]

LGTM, can we add a test case via failpoint to return WriteConflictError once?

I'll add one

[coocood]

LGTM

[cfzjywxk]

/run-all-tests

[cfzjywxk]

/run-all-tests

[cfzjywxk]

@jackysp @lysu PTAL

[sre-bot]

/run-all-tests

[sre-bot]

cherry pick to release-3.0 failed

[sre-bot]

It seems that, not for sure, we failed to cherry-pick this commit to release-3.0. Please comment '/run-cherry-picker' to try to trigger the cherry-picker if we did fail to cherry-pick this commit before. @cfzjywxk PTAL.