Quick start updates

[likidu]

What is changed, added or deleted? (Required)

Update wordings, notes orders to the Quick Start for TiDB Self-Managed doc.

• Uses 1 for ordered list, as it will increase automatically and can avoid the manual calculation of the numbers for the list.
• Tries to move the NOTE section after the main content. Some of the notes should be after the major content as they are more like extended content.
• Revisited the wordings, such as the topology table.

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)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.4 (TiDB 8.4 versions)
• v8.3 (TiDB 8.3 versions)
• 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)

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

• This PR is translated from:
• Other reference link(s): Update TiDB quick start docs-cn#19570

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

[Oreoxmt]

Uses 1 for ordered list, as it will increase automatically and can avoid the manual calculation of the numbers for the list.

@likidu According to our Markdown Lint rules (https://github.com/pingcap/docs/blob/master/.markdownlint.yaml), ordered lists must use sequential numbering (1, 2, 3) rather than repeated 1.. The current format is causing a build failure at https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Fdocs%2Fpull_verify/detail/pull_verify/10066/pipeline/.

While both formats render identically in Markdown, we require explicit sequential numbering for several reasons:

1. It maintains source content readability
2. It ensures consistency with our existing documentation style
3. It facilitates precise cross-referencing between steps (e.g., "as shown in step 2")
4. It simplifies document maintenance and review

Please update the ordered lists to use sequential numbers instead of repeated 1.. For example:

1. First step
2. Second step
3. Third step

[Oreoxmt]

Please use bullet points (-) instead of ordered numbers (1., 2.) here because these items represent independent commands, not sequential steps that must be performed in order:

docs/quick-start-with-tidb.md

Lines 495 to 509 in 8234ff0

	- To view the currently deployed cluster list:
	{{< copyable "shell-regular" >}}
	```shell
	tiup cluster list
	```
	- To view the cluster topology and status:
	{{< copyable "shell-regular" >}}
	```shell
	tiup cluster display <cluster-name>
	```

[likidu]

Further updated the content to address the feedback.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-01-16 09:01:34.520966891 +0000 UTC m=+195565.976013058: ☑️ agreed by Oreoxmt.

[lilin90]

I'll make some minor updates soon.

[lilin90]

For reviewer: This is to align the output with that in Chinese docs.

[ti-chi-bot]

@xhebox: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

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-sigs/prow repository.

[lilin90]

/unhold

[lilin90]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lilin90

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 [lilin90]

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-8.5: #20048.