br: restore checksum shouldn't rely on backup checksum (#56712)

[ti-chi-bot]

This is an automated cherry-pick of #56712

What problem does this PR solve?

Issue Number: close #56373

Problem Summary:

What changed and how does it work?

1. Disable checksum by default only for snapshot backup process.
2. Keep checksum enabled for the rest
3. During snapshot restore, verify admin checksum by doing xor on all meta file checksums, so it doesn't rely on backup generating the CRC for the database.

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.

The default behavior of doing checksum during full backup has changed from enabled to disabled. 
The meaning of checksum flag is kind of ambiguous here, it doesn't mean we don't do the checksum of files when doing backup, instead we don't do checksum to compare from coprocessor side to the br side to improve the performance

[ti-chi-bot]

@ti-chi-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/unit-test	aa21365	link	true	/test unit-test
idc-jenkins-ci-tidb/build	aa21365	link	true	/test build
idc-jenkins-ci-tidb/check_dev_2	aa21365	link	true	/test check-dev2
idc-jenkins-ci-tidb/check_dev	aa21365	link	true	/test check-dev
idc-jenkins-ci-tidb/mysql-test	aa21365	link	true	/test mysql-test

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BornChanger

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:

• OWNERS [BornChanger]
• br/OWNERS [BornChanger]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-12-11 08:26:24.846010567 +0000 UTC m=+426974.934813109: ☑️ agreed by BornChanger.