release-8.1: sync the cloud docs to the latest version

[qiancai]

First-time contributors' checklist

• [ ] I've signed Contributor License Agreement that's required for repo owners to accept my contribution.

What is changed, added or deleted? (Required)

As in the title, this PR replaces the cloud doc files in the release-8.1 branch with the latest files in the release-7.5 branch.

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)
• [ ] v8.5 (TiDB 8.5 versions)
• [ ] v8.4 (TiDB 8.4 versions)
• [ ] v8.3 (TiDB 8.3 versions)
• [ ] v8.2 (TiDB 8.2 versions)
• [x] v8.1 (TiDB 8.1 versions)
• [ ] v7.5 (TiDB 7.5 versions)
• [ ] v7.1 (TiDB 7.1 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)

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

• This PR is translated from:
• 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[bot]]

[LGTM Timeline notifier]

Timeline:

• 2024-11-21 07:54:39.924715732 +0000 UTC m=+104667.544370247: :ballot_box_with_check: agreed by lilin90.

[qiancai]

/approve

[ti-chi-bot[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiancai

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](https://github.com/pingcap/docs/blob/release-8.1/OWNERS)~~ [qiancai] 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: base branch (release-8.1) needs to differ from target branch (release-8.1).