ddl: add lease for ingest distributed lock

[tangenta]

What problem does this PR solve?

Issue Number: close #55917

Problem Summary:

The distributed lock was acquired successfully, but it failed to be released. When DDL retried in the next round, it stuck at acquiring the same distributed lock.

What changed and how does it work?

Similar to existing mechanisms of DDL owner key or server info key, add a lease for the distributed lock

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 @tangenta. 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.

[codecov]

Codecov Report

Attention: Patch coverage is 46.87500% with 17 lines in your changes missing coverage. Please review.

Project coverage is 76.3397%. Comparing base (e87affb) to head (5f4d438).
Report is 920 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #56184        +/-   ##
================================================
+ Coverage   73.4116%   76.3397%   +2.9281%     
================================================
  Files          1601       1626        +25     
  Lines        444010     456817     +12807     
================================================
+ Hits         325955     348733     +22778     
+ Misses        98086      86622     -11464     
- Partials      19969      21462      +1493     

Flag	Coverage Δ
integration	52.2520% <46.8750%> (?)
unit	72.6682% <34.3750%> (+0.1924%)	⬆️

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

Components	Coverage Δ
dumpling	52.9478% <ø> (ø)
parser	∅ <ø> (∅)
br	65.4286% <ø> (+19.5424%)	⬆️

[lance6716]

add some unit tests using embedded etcd?

https://github.com/search?q=repo%3Apingcap%2Ftiflow%20embed.StartEtcd&type=code

[lance6716]

rest lgtm

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lance6716, wjhuang2016

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:

• pkg/ddl/OWNERS [lance6716,wjhuang2016]
• pkg/owner/OWNERS [wjhuang2016]

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-09-20 08:34:57.26843402 +0000 UTC m=+1209367.008857959: ☑️ agreed by wjhuang2016.
• 2024-09-24 08:45:21.27530744 +0000 UTC m=+1555591.015731378: ☑️ agreed by lance6716.

[wjhuang2016]

/retest

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.1: #59265.
But this PR has conflicts, please resolve them!