cluster: start pd,dm-master in sequentially

[9547]

What problem does this PR solve?

implement #1187

What is changed and how it works?

Start instances in serial for Raft related components
eg: PD has more strict restrictions on the capacity expansion process, that is, there should be only one node in the peer-join stage at most.

Ref https://github.com/tikv/pd/blob/d38b36714ccee70480c39e07126e3456b5fb292d/server/join/join.go#L179-L191

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Code changes

• Has exported function/method change
• Has exported variable/fields change
• Has interface methods change
• Has persistent data change

Side effects

• Possible performance regression
• Increased code complexity
• Breaking backward compatibility

Related changes

• Need to cherry-pick to the release branch
• Need to update the documentation

Release notes:

NONE

[9547]

@HunDunDM @lucklove PTAL

[lucklove]

/lgtm

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• lucklove

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 writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[9547]

/run-all-tests

[lucklove]

/merge

[ti-chi-bot]

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

Commit hash: 0489b84