simulator: scale-in and scale out test for store-limit-version=v2

[bufferflies]

What problem does this PR solve?

Issue Number: Close #xxx

What is changed and how does it work?

run 
tiup playground nightly --host localhost --kv.binpath ./bin/pd-simulator --kv=1 --db=0 --kv.config=./tikv.conf  --pd.config ./pd.conf

tikv.conf

case-name="scale-in-out"
sim-tick-interval="100ms"
store-io-per-second=100

pd.toml
[schedule]
max-store-down-time = "5m"
store-limit-version = "v2"

Check List

Tests

• Manual test (add detailed scripts or steps below)

• No code

Code changes

Side effects

Related changes

Release note

None.

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

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[ti-chi-bot]

PR needs rebase.

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/test-infra repository.

[LykxSassinator]

Suggested change

	Run with tiup playgroudn :
	Run with tiup playground:

[ti-chi-bot]

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/needs-linked-issue label, please provide the linked issue number on one line in the PR body, for example: Issue Number: close #123 or Issue Number: ref #456, multiple issues should use full syntax for each issue and be separated by a comma, like: Issue Number: close #123, ref #456.

_{📖 For more info, you can check the "Linking issues" section in the CONTRIBUTING.md.}