br: redact ak/sk in logging (#55622)

[ti-chi-bot]

This is an automated cherry-pick of #55622

What problem does this PR solve?

Issue Number: close #55273

Problem Summary:
log-backup: secrets may be directly logging to log when --send-credentials-to-tikv=false not set during starting log backup

What changed and how does it work?

Added a wrap of the storage info and redact ak/sk, now the logging woud not print them directly.

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.

Added a wrap of the storage info and redact ak/sk, now the logging woud not print them directly.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (release-6.5@7759463). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-6.5     #55779   +/-   ##
================================================
  Coverage               ?   73.9431%           
================================================
  Files                  ?       1097           
  Lines                  ?     354870           
  Branches               ?          0           
================================================
  Hits                   ?     262402           
  Misses                 ?      75882           
  Partials               ?      16586           

[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 [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-09-02 07:35:02.088485897 +0000 UTC m=+257026.606538823: ☑️ agreed by Leavrth.
• 2024-09-02 08:17:52.128589393 +0000 UTC m=+259596.646642319: ☑️ agreed by BornChanger.

[Leavrth]

/retest

[Leavrth]

/retest