bootstrap: add cluster_id to the mysql.tidb table

[YangKeao]

What problem does this PR solve?

Issue Number: close #59476

Problem Summary:

We need a mechanism to detect whether two TiDB servers are in the same tidb cluster. Adding the cluster_id to the mysql.tidb table is the most sutiable way. I've also considered other options in #59476 .

What changed and how does it work?

Add the cluster_id row to the mysql.tidb table.

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.

Insert the `cluster_id` to the `mysql.tidb` table.

[YangKeao]

/cc @benmeadowcroft

[ti-chi-bot]

@YangKeao: GitHub didn't allow me to request PR reviews from the following users: BenMeadowcroft.

Note that only pingcap members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

/cc @benmeadowcroft

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.

[codecov]

Codecov Report

Attention: Patch coverage is 85.00000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 74.8387%. Comparing base (397b0f2) to head (43a9ed8).
Report is 14 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #59511        +/-   ##
================================================
+ Coverage   73.0599%   74.8387%   +1.7788%     
================================================
  Files          1690       1740        +50     
  Lines        467367     479651     +12284     
================================================
+ Hits         341458     358965     +17507     
+ Misses       104902      98239      -6663     
- Partials      21007      22447      +1440     

Flag	Coverage Δ
integration	48.9721% <75.0000%> (?)
unit	72.3793% <85.0000%> (+0.1426%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	59.3700% <ø> (+13.5841%)	⬆️

[Defined2014]

Please fix the UT

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-02-13 07:06:56.339948129 +0000 UTC m=+513058.736170186: ☑️ agreed by Defined2014.
• 2025-02-13 07:08:55.598991631 +0000 UTC m=+513177.995213692: ☑️ agreed by lance6716.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Defined2014, lance6716, Leavrth, yudongusa

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [Defined2014,Leavrth,lance6716]
• br/OWNERS [Leavrth]
• pkg/ddl/OWNERS [lance6716]
• pkg/session/OWNERS [yudongusa]

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

[YangKeao]

/cherry-pick release-8.5

[ti-chi-bot]

@YangKeao: new pull request created to branch release-8.5: #65564.
But this PR has conflicts, please resolve them!

Details

In response to this:

/cherry-pick release-8.5

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.