dm: track table schema for online ddl when use binlog skip

[GMHDBJD]

What problem does this PR solve?

Issue Number: close #9587

What is changed and how it works?

• apply online ddl before track ddl

Root Cause

we track the original ddl when use binlog skip feature, if user skip the RENAME TABLE statement for an online DDL, they indeed want to skip the real ALTER TABLE statement, then we track the wrong statement.

Check List

Tests

• manually test

run a online ddl which make tidb failed
binlog skip -b binlog-pos(the pos of RENAME TABLE statement)
operate-schema get

table should have right schema

Questions

Will it cause performance regression or break compatibility?

Do you need to update user documentation, design documentation or monitoring documentation?

Release note

Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with `None`.

[lance6716]

Can you explain the root cause of issue in PR description

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [lance6716,okJiang]

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:

• 2023-09-08 03:24:40.691654743 +0000 UTC m=+2675045.240670731: ☑️ agreed by okJiang.
• 2023-09-08 04:00:32.88206913 +0000 UTC m=+2677197.431085119: ☑️ agreed by lance6716.

[GMHDBJD]

/merge

[ti-chi-bot]

@GMHDBJD: We have migrated to builtin LGTM and approve plugins for reviewing.

Please use /approve when you want approve this pull request.

The changes announcement: LGTM plugin changes

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 ti-community-infra/tichi repository.

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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