br: skip fresh check when user has specified --filter in restore full

[3pointer]

What problem does this PR solve?

Issue Number: close #51009

Problem Summary:
In previous when user doing a full restore. we add a check to make sure the cluster must be empty. but sometime user want to do a full restore with --filter. at that time we should not check the empty cluster anymore.

What changed and how does it work?

This PR skip the check when user has set the --filter argument manually.

Check List

Tests

• Unit test

• Integration test

• Manual test (add detailed scripts or steps below)
  before this PR
  
  after this PR
  

• 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.

Fix the issue that makes --filter argument skip empty cluster check during full restore

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[tiprow]

Hi @3pointer. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[codecov]

Codecov Report

Merging #51010 (4b7c808) into master (f5e0799) will increase coverage by 0.3675%.
Report is 2 commits behind head on master.
The diff coverage is 66.6666%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #51010        +/-   ##
================================================
+ Coverage   72.2813%   72.6489%   +0.3675%     
================================================
  Files          1467       1467                
  Lines        361854     434919     +73065     
================================================
+ Hits         261553     315964     +54411     
- Misses        80989      99019     +18030     
- Partials      19312      19936       +624     

Flag	Coverage Δ
integration	49.1727% <0.0000%> (?)
unit	70.2973% <66.6666%> (-1.8581%)	⬇️

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

Components	Coverage Δ
dumpling	54.2940% <ø> (-2.1832%)	⬇️
parser	∅ <ø> (∅)
br	51.2297% <66.6666%> (+4.9433%)	⬆️

[BornChanger]

Please add a case. Other LGTM.

[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:

• 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-02-07 05:40:51.590757947 +0000 UTC m=+335377.157527840: ☑️ agreed by Leavrth.
• 2024-02-07 07:31:35.324355433 +0000 UTC m=+342020.891125325: ☑️ agreed by BornChanger.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #51041.