backup: use history iterator to scan ddl jobs

[3pointer]

What problem does this PR solve?

Issue Number: close #54139

Problem Summary:
sometimes cluster might have too many ddl jobs. backup should skip unnecessary scan of ddl jobs during the backup incremental ddls.

What changed and how does it work?

Use GetLastHistoryDDLJobsIterator instead of GetAllDDLJobs.

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

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

[3pointer]

/ok-to-test

[codecov]

Codecov Report

Attention: Patch coverage is 81.13208% with 10 lines in your changes missing coverage. Please review.

Project coverage is 56.8392%. Comparing base (a8de589) to head (034298f).
Report is 1010 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #54100         +/-   ##
=================================================
- Coverage   72.8399%   56.8392%   -16.0008%     
=================================================
  Files          1516       1643        +127     
  Lines        434775     611676     +176901     
=================================================
+ Hits         316690     347672      +30982     
- Misses        98499     240326     +141827     
- Partials      19586      23678       +4092     

Flag	Coverage Δ
integration	38.1171% <77.3584%> (?)
unit	71.7927% <81.1320%> (-0.0332%)	⬇️

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

Components	Coverage Δ
dumpling	52.9656% <ø> (ø)
parser	∅ <ø> (∅)
br	62.7920% <81.1320%> (+16.6659%)	⬆️

[3pointer]

/ok-to-test

[Leavrth]

should count counts the filtered jobs? count += len(jobs)

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [Leavrth,YuJuncen]

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-06-24 09:27:28.73880203 +0000 UTC m=+625375.224290854: ☑️ agreed by Leavrth.
• 2024-06-24 09:58:39.058087688 +0000 UTC m=+627245.543576520: ☑️ agreed by YuJuncen.

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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