credits: remove outdated contributor link and repos

[lilin90]

What is changed, added or deleted? (Required)

• Remove an outdated link of contributors, which does not work now
• Update the list of repos because multiple repos have been combined or migrated to another repo
  Note: All the changed will be cherry picked to v6.5, v6.6, v7.0 according to the repo archive date, while the change of removing the outdated contributor link will be cherry picked to all selected versions. The docs-dm repo link will be kept for v5.3 and earlier versions.

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

• master (the latest development version)
• v7.1 (TiDB 7.1 versions)
• v7.0 (TiDB 7.0 versions)
• v6.6 (TiDB 6.6 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 versions)
• v5.3 (TiDB 5.3 versions)
• v5.2 (TiDB 5.2 versions)
• v5.1 (TiDB 5.1 versions)
• v5.0 (TiDB 5.0 versions)

What is the related PR or file link(s)?

• This PR is translated from: credits: remove outdated contributor link and repos docs-cn#13776
• Other reference link(s):
  • README: prepare to archive project dm dm#2276, https://docs.pingcap.com/tidb-data-migration/v5.3
  • readme: move this repo to tidb br#1421
  • README: display a notice that the repository has been moved tidb-lightning#571
  • *: Dumpling merged into TiDB dumpling#379
  • README.md: mention this repo has been moved to pingcap/tidb parser#1372

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• Oreoxmt

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.

Details

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

[Oreoxmt]

LGTM

[lilin90]

/merge

[ti-chi-bot]

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

Details

Commit hash: b7aeb73

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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