feat: hide the non-full support level drivers/ORMs

[Icemap]

What is changed, added or deleted? (Required)

To avoid misunderstandings and ambiguities, we plan to remove "Compatible" level libraries. This does not mean that we are not compatible with removed third-party libraries. Removing "Compatible" simply means that we want to maintain a shorter list, allowing us to emphasize libraries that we have fully tested. The removed third-party libraries are that "PingCAP" has not completed a full test on all features of the tool, which might lead to some unexpected behaviors.

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.2 (TiDB 7.2 versions)
• 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: feat: hide the non-full support level drivers/ORMs docs-cn#14152
• Other reference link(s):

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]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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 kubernetes/test-infra repository.

[ti-chi-bot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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 kubernetes/test-infra repository.

[ti-chi-bot]

PR needs rebase.

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 kubernetes/test-infra repository.

[qiancai]

Removed the needs-cherry-pick-release-6.6 label because the v6.6 docs have been archived at https://docs-archive.pingcap.com/tidb/v6.6 and will no longer receive new updates.

[Oreoxmt]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Oreoxmt

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:

• develop/OWNERS [Oreoxmt]

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]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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