ddl: watch the ddl ownerkey with the createRevision

[joccau]

What problem does this PR solve?

A tidb-server run campaignOwner successfully and become owner. If it watches the owner after the ownerKey is deleted, the watchOwner() will be stuck.
The method to fix it: need to watch the owner since createRevision.

Issue Number: close #54689, ref #54436

Problem Summary:

What changed and how does it work?

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.

Watch the DDL ownerKey since createRevision after campaignOwner and become owner successfully.

[codecov]

Codecov Report

Attention: Patch coverage is 82.75862% with 5 lines in your changes missing coverage. Please review.

Project coverage is 56.3741%. Comparing base (df02db0) to head (ac35a00).
Report is 18 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #55692         +/-   ##
=================================================
- Coverage   72.9210%   56.3741%   -16.5469%     
=================================================
  Files          1585       1713        +128     
  Lines        443451     620011     +176560     
=================================================
+ Hits         323369     349526      +26157     
- Misses       100237     246895     +146658     
- Partials      19845      23590       +3745     

Flag	Coverage Δ
integration	37.4624% <51.7241%> (?)
unit	71.9127% <79.3103%> (-0.1376%)	⬇️

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

Components	Coverage Δ
dumpling	52.9567% <ø> (ø)
parser	∅ <ø> (∅)
br	52.2561% <ø> (+6.8046%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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/owner/OWNERS [D3Hunter]

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-03 02:48:12.408198258 +0000 UTC m=+326216.926251181: ☑️ agreed by D3Hunter.
• 2024-09-04 02:21:01.705553049 +0000 UTC m=+410986.223605972: ☑️ agreed by lance6716.

[joccau]

/test check-dev

[tiprow]

@joccau: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test check-dev

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.

[joccau]

Ref #54436