Make warmup failure/skip on corruption configurable (#5622)

[ti-chi-bot]

This is an automated cherry-pick of #5622

What problem does this PR solve?

Currently warmup script exits w/ error when it encounters corruption. Similar to #5621, this behavior makes sense for checking viability of backups, but conflicts w/ desire to perform a full restore and recover.

When we perform a full restore, if restore encounters corruption, warmup will fail and will cancel the actual warmup of the volumes. Desired behavior is to log the corruption but continue the warmup operation, so that, when complete, if there is only a single corrupt TiKV, we can attempt to recover using functionality added in #5585.

What is changed and how does it work?

Change updates warmup script to only exit/cancel warmup when encountering corruption when explicitly enabled. This is only enabled for check-wal-only strategy. Otherwise, we only log the corruption but continue with normal warmup.

Code changes

• [x] Has Go code change
• [ ] Has CI related scripts change

Tests

• [x] Unit test
• [ ] E2E test
• [ ] Manual test
• [ ] No code

Side effects

• [ ] Breaking backward compatibility
• [ ] Other side effects:

Related changes

• [ ] Need to cherry-pick to the release branch
• [ ] Need to update the documentation

Release Notes

Please refer to Release Notes Language Style Guide before writing the release note.

[ti-chi-bot[bot]]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign fengou1 for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/pingcap/tidb-operator/blob/release-1.5/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment