ttl: fix the issue that DROP TABLE / ALTER TABLE will keep job running

[YangKeao]

What problem does this PR solve?

Issue Number: close #57556, close #57702

Problem Summary:

If the TTL job owner restarts and the TTL table is disabled or dropped, it'll not be removed and will always keep running.

What changed and how does it work?

1. Also remove the table even when it's current status is not NULL if its heartbeat has timeout.
2. Shorten the GC period to 10 minutes.

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.

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[hawkingrei]

/retest

[hawkingrei]

/test all

[codecov]

Codecov Report

Attention: Patch coverage is 88.88889% with 1 line in your changes missing coverage. Please review.

Project coverage is 73.8402%. Comparing base (d02d48a) to head (c8fce98).
Report is 34 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #57707        +/-   ##
================================================
+ Coverage   72.8318%   73.8402%   +1.0083%     
================================================
  Files          1677       1677                
  Lines        463944     468364      +4420     
================================================
+ Hits         337899     345841      +7942     
+ Misses       105169     101855      -3314     
+ Partials      20876      20668       -208     

Flag	Coverage Δ
integration	44.0364% <77.7777%> (?)
unit	72.7075% <77.7777%> (+0.4836%)	⬆️

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

Components	Coverage Δ
dumpling	52.7673% <ø> (ø)
parser	∅ <ø> (∅)
br	46.2687% <ø> (+0.7575%)	⬆️

[tiprow]

@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
fast_test_tiprow	c8fce98	link	true	/test fast_test_tiprow

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.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Defined2014, 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 [Defined2014,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:

• 2024-11-27 06:04:41.279447175 +0000 UTC m=+616468.899101676: ☑️ agreed by lcwangchao.
• 2024-11-27 06:09:47.148759775 +0000 UTC m=+616774.768414291: ☑️ agreed by Defined2014.

[ti-chi-bot]

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