WIP: statistics: add the analysis worker

[Rustin170506]

What problem does this PR solve?

Issue Number: close #55618

Problem Summary:

This is a POC PR for #55618.

In this PR we introduced started tracking the current running tables within the refresher.
We also started always running N analysis jobs in TiDB instead of blocking the whole process in the HandleAutoAnalyze.

What changed and how does it work?

• An analysis worker was added for the statistics refresher.
• The analysis jobs are always spawned whenever possible.

Check List

Tests

• Unit test(TBD)
• 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 78.41727% with 30 lines in your changes missing coverage. Please review.

Project coverage is 74.5355%. Comparing base (1bf01f4) to head (db3afd2).
Report is 86 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #55621        +/-   ##
================================================
- Coverage   74.8168%   74.5355%   -0.2813%     
================================================
  Files          1581       1615        +34     
  Lines        367361     452007     +84646     
================================================
+ Hits         274848     336906     +62058     
- Misses        72653      94169     +21516     
- Partials      19860      20932      +1072     

Flag	Coverage Δ
integration	50.4808% <28.0575%> (?)
unit	71.8637% <78.4172%> (-1.9236%)	⬇️

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

Components	Coverage Δ
dumpling	52.9567% <ø> (-2.2327%)	⬇️
parser	∅ <ø> (∅)
br	49.7525% <ø> (+1.9847%)	⬆️

[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 assign qw4990 for approval. 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/planner/OWNERS
• 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

[ti-chi-bot]

@Rustin170506: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/mysql-test	db3afd2	link	true	/test mysql-test
pull-lightning-integration-test	db3afd2	link	true	/test pull-lightning-integration-test

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[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.