playground: fix tiproxy scale

[xhebox]

What problem does this PR solve?

missing sanitizeComponentConfig.

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:

Fix tiproxy playground scale out

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.91%. Comparing base (38b6c96) to head (5913469).

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

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2365      +/-   ##
==========================================
+ Coverage   55.77%   55.91%   +0.14%     
==========================================
  Files         329      329              
  Lines       35025    35032       +7     
==========================================
+ Hits        19534    19586      +52     
+ Misses      13154    13110      -44     
+ Partials     2337     2336       -1     

Flag	Coverage Δ
cluster	45.13% <ø> (-0.18%)	⬇️
dm	25.51% <ø> (-0.05%)	⬇️
playground	15.79% <100.00%> (+0.62%)	⬆️
tiup	33.60% <ø> (-0.05%)	⬇️
unittest	22.24% <0.00%> (-0.01%)	⬇️

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kaaaaaaang]

/lgtm

[kaaaaaaang]

/approve

[ti-chi-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 [kaaaaaaang]

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

[xhebox]

/retest

[kaaaaaaang]

/lgtm

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-01-29 05:56:06.194282659 +0000 UTC m=+1372207.758580688: ☑️ agreed by kaaaaaaang.
• 2024-01-29 07:03:52.465732209 +0000 UTC m=+1376274.030029909: ✖️🔁 reset by ti-chi-bot[bot].
• 2024-02-29 09:45:23.840984442 +0000 UTC m=+1128012.588607554: ☑️ agreed by kaaaaaaang.

[kaaaaaaang]

/approve