ticdc/owner: Fix ddl special comment syntax error (#3845)

[sdojjy]

This is an automated cherry-pick of #3845

What problem does this PR solve?

close https://github.com/pingcap/ticdc/issues/3755

What is changed and how it works?

not use regex to parse and add special TiDB comments, If a DDL already has special comment like /*!90000 SHARD_ROW_ID_BITS=4 PRE_SPLIT_REGIONS=3 */, it wil translate that DDL to /*!90000 /*T! SHARD_ROW_ID_BITS=4 PRE_SPLIT_REGIONS=3 */ */, TiDB will throw a syntax error.
this PR use the TiDB SQL parser to parse the SQL and the Restore it with format.RestoreStringSingleQuotes|format.RestoreNameBackQuotes|format.RestoreKeyWordUppercase|format.RestoreTiDBSpecialComment flag

Check List

Tests

• Unit test

Code changes

• Has exported function/method change
• Has exported variable/fields change
• Has interface methods change
• Has persistent data change

Side effects

• Possible performance regression
• Increased code complexity
• Breaking backward compatibility

Related changes

• Need to cherry-pick to the release branch
• Need to update the documentation
• Need to update key monitor metrics in both TiCDC document and official document

Release note

Fix syntax error if DDL has a special comment.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• amyangfei

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.

[sdojjy]

/run-unit-test

[codecov-commenter]

Codecov Report

Merging #4415 (f904620) into release-5.1 (8957631) will increase coverage by 0.1010%.
The diff coverage is 64.7058%.

@@                 Coverage Diff                 @@
##           release-5.1      #4415        +/-   ##
===================================================
+ Coverage      62.1198%   62.2209%   +0.1010%     
===================================================
  Files              161        161                
  Lines            16869      16885        +16     
===================================================
+ Hits             10479      10506        +27     
+ Misses            5491       5475        -16     
- Partials           899        904         +5     

[overvenus]

Can we use pingcap/parser?

[overvenus]

/hold

Since pingcap/parser does not support RestoreTiDBSpecialComment yet, we should be careful for using tidb/parser, as it may have side effect init().