tiproxy not use nightly by default

[nexustar]

What problem does this PR solve?

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: 1 lines in your changes are missing coverage. Please review.

Comparison is base (310afd1) 55.39% compared to head (42ac4bc) 50.17%.

❗ Current head 42ac4bc differs from pull request most recent head 0e25187. Consider uploading reports for the commit 0e25187 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2305      +/-   ##
==========================================
- Coverage   55.39%   50.17%   -5.21%     
==========================================
  Files         325      324       -1     
  Lines       34706    34693      -13     
==========================================
- Hits        19222    17406    -1816     
- Misses      13185    15004    +1819     
+ Partials     2299     2283      -16     

Flag	Coverage Δ
tiup	15.56% <0.00%> (+<0.01%)	⬆️
unittest	?

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

Files	Coverage Δ
components/playground/main.go	59.24% <ø> (ø)
components/playground/playground.go	44.31% <ø> (+0.04%)	⬆️
pkg/cluster/spec/tiproxy.go	4.35% <0.00%> (-0.46%)	⬇️

... and 59 files with indirect coverage changes

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

[kaaaaaaang]

/lgtm

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-11-08 10:17:32.991168287 +0000 UTC m=+3639450.578278466: ☑️ agreed by kaaaaaaang.

[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