ttl: don't GC running TTL jobs

[YangKeao]

What problem does this PR solve?

Issue Number: close #58642

Problem Summary:

What changed and how does it work?

As mentioned in #58539, a better solution to #58510 is to not remove running TTL jobs in GC, but let the owner to finish the job.

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

[codecov]

Codecov Report

Attention: Patch coverage is 83.09859% with 12 lines in your changes missing coverage. Please review.

Project coverage is 73.5165%. Comparing base (b71ad38) to head (d7f8588).
Report is 17 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #58644        +/-   ##
================================================
+ Coverage   73.1612%   73.5165%   +0.3552%     
================================================
  Files          1676       1676                
  Lines        463532     464142       +610     
================================================
+ Hits         339126     341221      +2095     
+ Misses       103600     102047      -1553     
- Partials      20806      20874        +68     

Flag	Coverage Δ
integration	42.8419% <2.8169%> (?)
unit	72.3071% <83.0985%> (-0.0485%)	⬇️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	45.4802% <ø> (-0.3252%)	⬇️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lcwangchao

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 [lcwangchao]

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:

• 2025-01-02 03:23:04.109481194 +0000 UTC m=+579919.465485738: ☑️ agreed by lcwangchao.

[ti-chi-bot]

@YangKeao: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/build	60af5b3	link	true	/test build

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.