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.

None

[codecov]

Codecov Report

Attention: Patch coverage is 60.46512% with 34 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-8.5@dfaec68). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-8.5     #57503   +/-   ##
================================================
  Coverage               ?   57.0849%           
================================================
  Files                  ?       1770           
  Lines                  ?     627917           
  Branches               ?          0           
================================================
  Hits                   ?     358446           
  Misses                 ?     245449           
  Partials               ?      24022           

Flag	Coverage Δ
integration	36.9547% <63.5135%> (?)
unit	72.7652% <30.2325%> (?)

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

Components	Coverage Δ
dumpling	52.9478% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	52.3287% <0.0000%> (?)

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[Tristan1900]

/assign @BornChanger

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BornChanger, Leavrth

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,Leavrth]
• br/OWNERS [BornChanger,Leavrth]

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-11-19 15:58:53.062006428 +0000 UTC m=+976695.252875426: ☑️ agreed by Leavrth.
• 2024-11-19 23:54:46.210075558 +0000 UTC m=+1005248.400944551: ☑️ agreed by BornChanger.

[Tristan1900]

/retest