br: modify collate.newCollationEnabled according to the config of the cluster (#39173)

[ti-chi-bot]

This is an automated cherry-pick of #39173

What problem does this PR solve?

Issue Number: close #39150

Problem Summary:
The collate.newCollationEnabled variable is set to 1 when the collate package is initialized. When using this package, this value is not modified according to the config of the TiDB cluster (i.e., new_collations_enabled_on_first_bootstrap).

As a result, the user sets new_collations_enabled_on_first_bootstrap to false in the TiDB cluster, and it is still treated as true when br is executed.

What is changed and how it works?

Modify collate.newCollationEnabled according to the config of the cluster.

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

Manual test

• create a cluster with tidb config new_collations_enabled_on_first_bootstrap: false.
• create a table with collation 'utf8mb4_0900_ai_ci': create table books (id bigint auto_increment,name varchar(64), primary key (id)) CHARSET utf8mb4 COLLATE utf8mb4_0900_ai_ci;
• insert several records to the table.
• execute a full backup
• create another cluster tidb config new_collations_enabled_on_first_bootstrap: false.
• restore the backup to the new cluster => success

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

Fix a bug that: "Error Unsupported collation when new collation is enabled: 'utf8mb4_0900_ai_ci'" even if new_collation_enabled is false.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• 3pointer
• fengou1

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.

[YuJuncen]

/merge

[ti-chi-bot]

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

Commit hash: 69abddf

[MoCuishle28]

/run-all-tests

[MoCuishle28]

/run-mysql-test

[3pointer]

/run-check_dev

[MoCuishle28]

/run-mysql-test

[wuhuizuo]

/run-build

[MoCuishle28]

/run-mysql-test

[Ivy-YinSu]

/run-mysql-test

[Ivy-YinSu]

/run-check_dev

[ti-chi-bot]

@ti-chi-bot: 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.

[Ivy-YinSu]

/run-check_dev

[MoCuishle28]

/run-unit-test

[Ivy-YinSu]

/run-check_dev
/run-unit-test

[Ivy-YinSu]

/run-check_dev