dep(dm): move column-mapping from tidb-tools to tiflow repo

[lance6716]

What problem does this PR solve?

Issue Number: close #11114

What is changed and how it works?

column-mapping is a dead package, we won't develop its feature in future, so the duplication of code with tidb-tools is fine because the code will not change.

Check List

Tests

• No code

Questions

Will it cause performance regression or break compatibility?

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

Release note

`None`.

[3AceShowHand]

please create new issue for each PR, this makes the cherry-pick process easier.

[lance6716]

/check-issue-triage-complete

[lance6716]

/retest

[codecov]

Codecov Report

Attention: Patch coverage is 66.97248% with 108 lines in your changes are missing coverage. Please review.

Project coverage is 57.5742%. Comparing base (aed7768) to head (3e30fc2).
Report is 1 commits behind head on master.

Additional details and impacted files

Components	Coverage Δ
cdc	61.9940% <66.9724%> (+0.0400%)	⬆️
dm	51.2349% <ø> (-0.0102%)	⬇️
engine	63.4161% <ø> (+0.0070%)	⬆️

Flag	Coverage Δ
unit	57.5742% <66.9724%> (+0.0276%)	⬆️

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

@@               Coverage Diff                @@
##             master     #11112        +/-   ##
================================================
+ Coverage   57.5466%   57.5742%   +0.0276%     
================================================
  Files           853        854         +1     
  Lines        125679     126006       +327     
================================================
+ Hits          72324      72547       +223     
- Misses        47986      48068        +82     
- Partials       5369       5391        +22     

[lance6716]

/retest

[3AceShowHand]

/retest

[D3Hunter]

are all code copied from tidb repo?

[lance6716]

tidb-tools. And the test files are changed to require package

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-05-16 06:17:21.277902873 +0000 UTC m=+1720395.035038447: ☑️ agreed by 3AceShowHand.
• 2024-05-16 06:31:13.101421022 +0000 UTC m=+1721226.858556580: ☑️ agreed by okJiang.

[lance6716]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 3AceShowHand, 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 [3AceShowHand,lance6716,okJiang]
• dm/OWNERS [lance6716]
• engine/OWNERS [lance6716]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[lance6716]

/retest

[3AceShowHand]

/cherry-pick release-7.5

[ti-chi-bot]

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

[ti-chi-bot]

@3AceShowHand: new pull request could not be created: failed to create pull request against pingcap/tiflow#release-7.5 from head ti-chi-bot:cherry-pick-11112-to-release-7.5: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for ti-chi-bot:cherry-pick-11112-to-release-7.5."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"}

In response to this:

/cherry-pick release-7.5

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-8.1: #11454.