cluster: check support check before scale-out the instance

[srstack]

What problem does this PR solve?

close #1621

What is changed and how it works?

1. check should support check with the scale-out topology file

tiup cluster check cluster-name  scale-out.yml  --cluster 

2. Increase the detection of the existence of deployment directories, daily directories, data directories and systemdUnit file to prevent conflicts in tidb clusters deployed in different ways
   
3. Added prompts for scale-out operations
   

Check List

Tests

• Manual test (add detailed scripts or steps below)

Code changes

• Has exported function/method change

Side effects

• Increased code complexity

Related changes

• Need to update the documentation

Release notes:

NONE

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• AstroProfundis

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.

[codecov-commenter]

Codecov Report

Merging #1659 (beaebf2) into master (13b33c0) will increase coverage by 22.24%.
The diff coverage is 6.82%.

❗ Current head beaebf2 differs from pull request most recent head d88ea75. Consider uploading reports for the commit d88ea75 to get more accurate results

@@             Coverage Diff             @@
##           master    #1659       +/-   ##
===========================================
+ Coverage   24.50%   46.74%   +22.24%     
===========================================
  Files         277      303       +26     
  Lines       31291    34189     +2898     
===========================================
+ Hits         7667    15980     +8313     
+ Misses      22776    16337     -6439     
- Partials      848     1872     +1024     

Flag	Coverage Δ
cluster	32.66% <6.82%> (?)
dm	23.20% <3.36%> (?)
playground	12.76% <ø> (?)
tiup	14.62% <ø> (ø)
unittest	21.33% <4.50%> (-0.04%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
pkg/cluster/manager/scale_out.go	41.71% <0.00%> (+36.37%)	⬆️
pkg/cluster/operation/check.go	0.00% <0.00%> (ø)
pkg/cluster/task/check.go	0.00% <0.00%> (ø)
pkg/cluster/manager/check.go	0.74% <4.40%> (+0.74%)	⬆️
components/cluster/command/check.go	66.67% <38.46%> (-10.48%)	⬇️
components/dm/task/update_dm_meta.go	87.76% <0.00%> (ø)
pkg/cluster/operation/scale_in.go	50.00% <0.00%> (ø)
components/playground/instance/tiflash.go	55.56% <0.00%> (ø)
... and 190 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 13b33c0...d88ea75. Read the comment docs.

[AstroProfundis]

Should use RootSSH instead of UserSSH for pre-scale-out checks, as those host may have no deploy user created.

[srstack]

Should use RootSSH instead of UserSSH for pre-scale-out checks, as those host may have no deploy user created.

When checking an existing cluster, the ssh user will be forcibly set to metadata.User, which makes it impossible to log in with the root.
Now special treatment has been done for scale-out topology.

[AstroProfundis]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: d88ea75