tiup version constraint added to faq

[mjonss]

What is changed, added or deleted? (Required)

Added an answer about tiup version constraints

close #7565

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.

• [X] master (the latest development version)
• [ ] 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)
• [ ] v4.0 (TiDB 4.0 versions)
• [ ] v3.1 (TiDB 3.1 versions)
• [ ] v3.0 (TiDB 3.0 versions)
• [ ] v2.1 (TiDB 2.1 versions)

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

• This PR is translated from:
• Other reference link(s):

https://github.com/pingcap/tiup/blob/382d0e95f1c68e2fe272266d77abd57f273f7f31/pkg/utils/semver.go#L120

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 not been approved.

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.

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

[shichun-0415]

@mjonss According to confirmation with @AstroProfundis, the method you described in this PR to specify the latest patch version will be deprecated in the future. Therefore, it is better not to mention it in documents.

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

@mjonss After confirming with @kaaaaaaang, this method you described in this PR to specify the latest patch version is exclusively supported by tiup playground and not tiup cluster. Additionally, this method might not have undergone comprehensive testing and it's not recommended for users to use this. Consequently, I will proceed to close this PR."