tiup, tiproxy: add version flags to tiup cluster upgrade (#16917)

[ti-chi-bot]

This is an automated cherry-pick of #16917

What is changed, added or deleted? (Required)

• TiUP Cluster supports specifying versions of specific components:

Flags:
      --alertmanager-version string        Fix the version of alertmanager and no longer follows the cluster version.
      --blackbox-exporter-version string   Fix the version of blackbox-exporter and no longer follows the cluster version.
      --cdc-version string                 Fix the version of cdc and no longer follows the cluster version.
      --force                              Force upgrade without transferring PD leader
  -h, --help                               help for upgrade
      --ignore-config-check                Ignore the config check result
      --ignore-version-check               Ignore checking if target version is bigger than current version
      --node-exporter-version string       Fix the version of node-exporter and no longer follows the cluster version.
      --offline                            Upgrade a stopped cluster
      --pd-version string                  Fix the version of pv and no longer follows the cluster version.
      --post-upgrade-script string         (EXPERIMENTAL) Custom script to be executed on each server after the server is upgraded
      --pre-upgrade-script string          (EXPERIMENTAL) Custom script to be executed on each server before the server is upgraded
      --tidb-dashboard-version string      Fix the version of tidb-dashboard and no longer follows the cluster version.
      --tiflash-version string             Fix the version of tiflash and no longer follows the cluster version.
      --tikv-cdc-version string            Fix the version of tikv-cdc and no longer follows the cluster version.
      --tikv-version string                Fix the version of tikv and no longer follows the cluster version.
      --tiproxy-version string             Fix the version of tiproxy and no longer follows the cluster version.
      --transfer-timeout uint              Timeout in seconds when transferring PD and TiKV store leaders, also for TiCDC drain one capture (default 600)

• Update the links in TiProxy overview doc

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 (in Chinese).

• master (the latest development version)
• v7.6 (TiDB 7.6 versions)
• v7.5 (TiDB 7.5 versions)
• v7.4 (TiDB 7.4 versions)
• v7.3 (TiDB 7.3 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)
• 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: tiup, tiproxy: add version flags to tiup cluster upgrade docs-cn#16243 and tiproxy: fix config require-backend-tls docs-cn#17081
• 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

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

• OWNERS [Oreoxmt]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment