statistics: handle lock and unlock operations correctly

[Rustin170506]

What problem does this PR solve?

Issue Number: ref #55906

Problem Summary:

What changed and how does it work?

This PR is based on #56437

Handle the lock and unlock operations correctly.

1. When we unlock the tables, we need to update the version in order to trigger an update, allowing the priority queue to check the latest count and the modify_count.
2. When we lock the tables, we need to update the version as well. This lets the priority queue know that the table has been changed, and we need to evaluate it again.
3. In the priority queue, when we enqueue the table, we will check if this table has been locked or unlocked.

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

[codecov]

Codecov Report

Attention: Patch coverage is 52.87356% with 41 lines in your changes missing coverage. Please review.

Project coverage is 56.4439%. Comparing base (fa723c3) to head (bc8c0e9).

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #56454         +/-   ##
=================================================
- Coverage   73.3500%   56.4439%   -16.9061%     
=================================================
  Files          1629       1779        +150     
  Lines        450090     636990     +186900     
=================================================
+ Hits         330141     359542      +29401     
- Misses        99710     252872     +153162     
- Partials      20239      24576       +4337     

Flag	Coverage Δ
integration	38.0533% <10.3448%> (?)
unit	72.4726% <52.8735%> (-0.0110%)	⬇️

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

Components	Coverage Δ
dumpling	52.9478% <ø> (ø)
parser	∅ <ø> (∅)
br	52.4037% <ø> (+6.8243%)	⬆️

[ti-chi-bot]

PR needs rebase.

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.

[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 rustin170506, 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:

• pkg/statistics/OWNERS

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

[Rustin170506]

/retest

[Rustin170506]

🔢 Self-check (PR reviewed by myself and ready for feedback.)

[Rustin170506]

🔢 Self-check (PR reviewed by myself and ready for feedback.)

[Rustin170506]

/retest