playground: Allow configuring pd.binpath for all PD microservices

[breezewish]

What problem does this PR solve?

Currently, in PD microservice mode, users must specify binPath for each microservice, e.g.:

--pd.api.binpath=xxx
--pd.tso.binpath=xxx
...

After this PR, user can use one binPath for all microservices:

--pd.binpath=xxx    # Effective to all microservices

Users are also allowed to override binPath for particular microservice:

--pd.binpath=xxx    # Effective to all microservices except for TSO
--pd.tso.binpath=yyy

What is changed and how it works?

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

[codecov-commenter]

Codecov Report

Attention: 8 lines in your changes are missing coverage. Please review.

Comparison is base (768dea3) 55.40% compared to head (468e619) 55.40%.

:exclamation: Current head 468e619 differs from pull request most recent head b04896e. Consider uploading reports for the commit b04896e to get more accurate results

Files	Patch %	Lines
components/playground/main.go	0.00%	8 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #2347 +/- ## ========================================== - Coverage 55.40% 55.40% -0.00% ========================================== Files 328 329 +1 Lines 34822 34836 +14 ========================================== + Hits 19291 19298 +7 - Misses 13225 13230 +5 - Partials 2306 2308 +2 ``` | [Flag](https://app.codecov.io/gh/pingcap/tiup/pull/2347/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pingcap) | Coverage Δ | | |---|---|---| | [playground](https://app.codecov.io/gh/pingcap/tiup/pull/2347/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pingcap) | `15.37% <0.00%> (+0.05%)` | :arrow_up: | | [tiup](https://app.codecov.io/gh/pingcap/tiup/pull/2347/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pingcap) | `33.56% <ø> (-0.05%)` | :arrow_down: | | [unittest](https://app.codecov.io/gh/pingcap/tiup/pull/2347/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pingcap) | `22.34% <0.00%> (-0.01%)` | :arrow_down: | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pingcap#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[ti-chi-bot[bot]]

@rleungx: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to [this](https://github.com/pingcap/tiup/pull/2347#pullrequestreview-1800059325): > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[kaaaaaaang]

/lgtm

[kaaaaaaang]

/approve

[ti-chi-bot[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kaaaaaaang

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](https://github.com/pingcap/tiup/blob/master/OWNERS)~~ [kaaaaaaang] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[ti-chi-bot[bot]]

[LGTM Timeline notifier]

Timeline:

• 2024-01-05 04:13:38.601087119 +0000 UTC m=+2403109.638314045: :ballot_box_with_check: agreed by kaaaaaaang.
• 2024-01-05 04:13:56.547707606 +0000 UTC m=+2403127.584934533: :heavy_multiplication_x::repeat: reset by ti-chi-bot[bot].

[ti-chi-bot[bot]]

@breezewish: Your PR was out of date, I have automatically updated it for you.

Instructions for interacting with me using PR comments are available [here](https://prow.tidb.net/command-help). If you have questions or suggestions related to my behavior, please file an issue against the [ti-community-infra/tichi](https://github.com/ti-community-infra/tichi/issues/new?title=Prow%20issue:) repository.

[ti-chi-bot[bot]]

New changes are detected. LGTM label has been removed.