*: track cluster-level analyze jobs and make it persistent

[xuyifangreeneyes]

What problem does this PR solve?

Issue Number: close #32403

Problem Summary:
show analyze status only shows analyze jobs on self instance and the previous analyze jobs are cleared after rebooting.

What is changed and how it works?

Previously analyze jobs are tracked in memory. In the PR we introduce a system table mysql.analyze_jobs and track analyze jobs in the system table. The implementation of show analyze status is changed to read recent 30 analyze jobs from mysql.analyze_jobs. In this way the analyze jobs are persistent even after rebooting TiDB. Besides, each TiDB server dumps analyze jobs into the same table so show analyze status shows cluster-level analyze jobs. We also introduce two more fields instance and process_id to indicate on which TiDB and which process the analyze job is executed.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• 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

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• time-and-fate
• winoros

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.

[xuyifangreeneyes]

/cc @chrysan @winoros @qw4990

[sre-bot]

Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/694be1edc582947e5bd0ea714da0bda84bc8b3e1

[qw4990]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 70f195f

[xuyifangreeneyes]

/run-unit-test

[ti-chi-bot]

@xuyifangreeneyes: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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.