syncer(dm): add collation config "collation_compatible"

[WizardXiao]

What problem does this PR solve?

Issue Number: close #3420

What is changed and how it works?

add config collation_compatible.
default loose handle create sql by original sql, will not add default collation as upstream.
strick will add default collation as upstream, and downstream will occur error when downstream don't support.

Check List

Tests

• Unit test
• Integration test

Related changes

• Need to update the documentation

Release note

add config `collation_compatible`.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• Ehco1996
• lance6716

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.

[WizardXiao]

i will fix integration test after add same config in dumpling.

[WizardXiao]

/run-all-tests

[Ehco1996]

LGTM after fix the it test, do wee need add this config to doc ?

[lance6716]

rest lgtm

[WizardXiao]

LGTM after fix the it test, do wee need add this config to doc ?

yes, this need add to doc, i will write doc pr.

[WizardXiao]

/run-all-tests

[WizardXiao]

/run-all-tests

[Ehco1996]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: f81d5db

[WizardXiao]

/run-all-tests

[lance6716]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 174e00e

[ti-chi-bot]

[FORMAT CHECKER NOTIFICATION]

Notice: Please provide the linked issue number on one line in the PR body, for example: Issue Number: close #123 or Issue Number: ref #456.

_{📖 For more info, you can check the "Contribute Code" section in the development guide.}

[ti-chi-bot]

@WizardXiao: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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.

[lance6716]

/run-leak-test

[codecov-commenter]

Codecov Report

Merging #4121 (174e00e) into master (08da001) will increase coverage by 0.1456%.
The diff coverage is 65.5935%.

❗ Current head 174e00e differs from pull request most recent head 7d9909e. Consider uploading reports for the commit 7d9909e to get more accurate results

Flag	Coverage Δ
cdc	58.8119% <67.7966%> (+0.1671%)	⬆️
dm	52.3334% <58.1497%> (+0.0788%)	⬆️

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

@@               Coverage Diff                @@
##             master      #4121        +/-   ##
================================================
+ Coverage   55.1722%   55.3179%   +0.1456%     
================================================
  Files           485        489         +4     
  Lines         59829      60550       +721     
================================================
+ Hits          33009      33495       +486     
- Misses        23484      23684       +200     
- Partials       3336       3371        +35     

[lance6716]

/run-kafka-integration-test
/run-verify

[WizardXiao]

/run-kafka-integration-test

[ti-chi-bot]

In response to a cherrypick label: new pull request created: #4388.