ddl: wait schema change before rename table job is done (#43341)

[ti-chi-bot]

This is an automated cherry-pick of #43341

What problem does this PR solve?

Issue Number: close #43338

Problem Summary:

What is changed and how it works?

We split the renaming table job into two steps:

1. rename table and update the schema version.
2. update the job state to JobStateDone.

This is the requirement from TiCDC because

• it uses the job state to check whether the DDL is finished.
• there is a gap between schema reloading and job state updating:
  when the job state is updated to JobStateDone, before the new schema reloaded,
  there may be DMLs that use the old schema.
• TiCDC cannot handle the DMLs that use the old schema, because
  the commit TS of the DMLs are greater than the job state updating TS.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

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

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.