ttl: fix the issue that the task is not cancelled after transfering owners (#57788)

[ti-chi-bot]

This is an automated cherry-pick of #57788

What problem does this PR solve?

Issue Number: close #57784

Problem Summary:

The TTL task is not cancelled after the owner transfers to other TiDB nodes.

What changed and how does it work?

1. Don't report status when the owner is not myself.
2. Don't update heartbeat when the owenr is not myself.
3. Check the affected rows to see whether task manager UPDATE successfully.
4. Cancel the task after finding that the owner is not myself.

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

[codecov]

Codecov Report

Attention: Patch coverage is 85.18519% with 4 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-7.5@1f0d8ff). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-7.5     #59395   +/-   ##
================================================
  Coverage               ?   72.1628%           
================================================
  Files                  ?       1417           
  Lines                  ?     413494           
  Branches               ?          0           
================================================
  Hits                   ?     298389           
  Misses                 ?      95096           
  Partials               ?      20009           

Flag	Coverage Δ
unit	72.1628% <85.1851%> (?)

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

Components	Coverage Δ
dumpling	52.9400% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	53.4845% <0.0000%> (?)

[ti-chi-bot]

@lcwangchao: Your lgtm message is repeated, so it is ignored.

In response to this:

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.

[YangKeao]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lcwangchao, YangKeao

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 [YangKeao,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-02-11 07:43:10.685612397 +0000 UTC m=+342433.081834451: ☑️ agreed by lcwangchao.
• 2025-02-11 07:55:50.114500418 +0000 UTC m=+343192.510722479: ☑️ agreed by YangKeao.

[YangKeao]

/unhold