sessionctx: mark tidb_enable_auto_analyze_priority_queue as deprecated

[Rustin170506]

What problem does this PR solve?

Issue Number: ref #50132

Problem Summary:

What changed and how does it work?

Mark tidb_enable_auto_analyze_priority_queue is deprecated. We will always use it in the future because, compared to random selection, it is always better.

Check List

Tests

• Unit test
• Integration test
• Manual test
• 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.

将 tidb_enable_auto_analyze_priority_queue 标记为废弃。
Mark tidb_enable_auto_analyze_priority_queue as deprecated.

[Rustin170506]

Tested locally:

1. Start the cluster with patch: tiup playground v8.1.0 --db.binpath /Volumes/t7/code/tidb/bin/tidb-server
2. Try to set tidb_enable_auto_analyze_priority_queue:

mysql> set global tidb_enable_auto_analyze_priority_queue = 'OFF';
Query OK, 0 rows affected, 1 warning (0.01 sec)

mysql> show warnings;
+---------+------+----------------------------------------------------------------------------------------------------------------------------------------+
| Level   | Code | Message                                                                                                                                |
+---------+------+----------------------------------------------------------------------------------------------------------------------------------------+
| Warning | 1681 | tidb_enable_auto_analyze_priority_queue will be removed in the future and TiDB will always use priority queue to execute auto analyze. |
+---------+------+----------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

[Rustin170506]

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.9763%. Comparing base (e47330c) to head (28133e7).
Report is 11 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #54088         +/-   ##
=================================================
- Coverage   74.8056%   55.9763%   -18.8293%     
=================================================
  Files          1516       1636        +120     
  Lines        360862     605366     +244504     
=================================================
+ Hits         269945     338862      +68917     
- Misses        71325     243318     +171993     
- Partials      19592      23186       +3594     

Flag	Coverage Δ
integration	37.0218% <100.0000%> (?)
unit	71.7741% <100.0000%> (-1.9089%)	⬇️

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

Components	Coverage Δ
dumpling	52.9656% <ø> (-2.2339%)	⬇️
parser	∅ <ø> (∅)
br	52.6825% <ø> (+4.6877%)	⬆️

[elsa0520]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-06-18 15:07:40.44138599 +0000 UTC m=+127386.926874819: ☑️ agreed by elsa0520.
• 2024-06-18 15:55:57.809829156 +0000 UTC m=+130284.295317987: ☑️ agreed by hawkingrei.

[easonn7]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: easonn7, elsa0520, hawkingrei

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/sessionctx/variable/OWNERS [easonn7]

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