GC : fix issue of delete range could not be executed again if the cleaning rules failed (#53368)

[ystaticy]

This is an automated cherry-pick of #53368

What problem does this PR solve?
If the rules cleaning fails, it should not delete the ranges record from the gc_delete_range table.
Otherwise, it will cause the residue of rules, due to the delete range could not be executed again.

Issue Number: ref #53369

Problem Summary:

What changed and how does it work?

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

[tiprow]

Hi @ystaticy. 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-sigs/prow repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ekexium, MyonKeminta

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 [MyonKeminta,ekexium]

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-10-30 08:14:05.826207194 +0000 UTC m=+423958.665362732: ☑️ agreed by ekexium.
• 2024-10-31 03:08:35.793826226 +0000 UTC m=+492028.632981766: ☑️ agreed by MyonKeminta.

[ystaticy]

/test unit-test

[tiprow]

@ystaticy: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test unit-test

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-sigs/prow repository.

[codecov]

Codecov Report

Attention: Patch coverage is 11.11111% with 8 lines in your changes missing coverage. Please review.

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

Additional details and impacted files

@@               Coverage Diff                @@
##             release-6.5     #56983   +/-   ##
================================================
  Coverage               ?   73.6330%           
================================================
  Files                  ?       1097           
  Lines                  ?     352942           
  Branches               ?          0           
================================================
  Hits                   ?     259882           
  Misses                 ?      76340           
  Partials               ?      16720