*: implement analyze predicate columns

[xuyifangreeneyes]

What problem does this PR solve?

Issue Number: close #31102

Problem Summary:

What is changed and how it works?

What is changed?

1. Implement analyze table t predicate columns. When there is no predicate column for t, it gives a warning and falls back to analyze all columns.
2. Introduce global variable tidb_enable_column_tracking, which controls whether to collect predicate columns from SQL and dump to disk. When set global tidb_enable_column_tracking = 0, all the predicate columns collected before are invalidated.

How it works?

1. analyze table t predicate columns finds out predicate columns for t by reading from mysql.column_stats_usage. After figuring out which columns' stats need to be collected, the following thing is just the same as analyze table t columns c1, ..., cn.
2. When set global tidb_enable_column_tracking = 0, we don't physically update mysql.column_stats_usage to invalidate predicate columns. Instead, we record the time of the setting operation in tidb_disable_column_tracking_time, which is a variable in the system variable mysql.tidb. When we want to get predicate columns, we read from mysql.column_stats_usage and filter out the columns whose last_used_at is null. Then we compare last_used_at with tidb_disable_column_tracking_time. last_used_at <= tidb_disable_column_tracking_time means that the predicate columns is invalidated. So we only regard the columns whose last_used_at > tidb_disable_column_tracking_time as predicate columns.

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:

• qw4990
• 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 @winoros @chrysan

[sre-bot]

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

[xuyifangreeneyes]

/run-unit-test

[xuyifangreeneyes]

/run-check_dev_2

[winoros]

/merge

[ti-chi-bot]

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

Commit hash: f00e4a3

[xuyifangreeneyes]

/run-unit-test

[xuyifangreeneyes]

/run-check_dev_2