chore: supply a script to update tidb-dashboard

[baurine]

What problem does this PR solve?

Issue Number: Close #7612

What is changed and how does it work?

Because the tidb-dashboard repo may abandon to use release-version file to express its version, so we need to adjust the scripts to get tidb-dashbboard version.

This PR supplies a new script scripts/update-dashobard, when we need to update the tidb-dashobard in PD side, we just need to run the following command:

$ ./scripts/update-dashboard <new_dashboard_version>

Then commit and push the changes.

That ok, it simplifies the multiple steps before.

This script will persist a dashboard version in a file named scripts/dashboard-version, so now we can explicitly know which dashboard version this PD embeds, while we don't know before.

This PR also delete the scripts/embed-dashboard-ui.ps1 and build.ps1 files, which I think they are un-used anymore.

Release note

None.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• HuSharp
• rleungx

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]

Hi @baurine. Thanks for your PR.

I'm waiting for a tikv member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[codecov]

Codecov Report

Merging #7610 (627ba29) into master (d3551ea) will decrease coverage by 0.11%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7610      +/-   ##
==========================================
- Coverage   74.88%   74.78%   -0.11%     
==========================================
  Files         459      459              
  Lines       50647    50647              
==========================================
- Hits        37925    37874      -51     
- Misses       9385     9425      +40     
- Partials     3337     3348      +11     

Flag	Coverage Δ
unittests	74.78% <ø> (-0.11%)	⬇️

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

[baurine]

tidb-dashboard version will change to x.y.z (likes 7.6.0) style in the future, same as TiDB/TiKV/PD.

[baurine]

/cc @mornyx @shhdgit PTAL as well, thanks~

[HuSharp]

/ok-to-test

[ti-chi-bot]

@mornyx: Thanks for your review. The bot only counts approvals from reviewers and higher roles in list, but you're still welcome to leave your comments.

In response to this:

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 ti-community-infra/tichi repository.

[nolouch]

/merge

[ti-chi-bot]

@nolouch: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

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 ti-community-infra/tichi repository.

[ti-chi-bot]

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

Commit hash: 160a6f3

[ti-chi-bot]

@baurine: new pull request created to branch release-7.5: #7632.

In response to this:

/cherry-pick release-7.5

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 ti-community-infra/tichi repository.

[ti-chi-bot]

@baurine: new pull request created to branch release-7.1: #7633.

In response to this:

/cherry-pick release-7.1

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 ti-community-infra/tichi repository.

[baurine]

/cherry-pick release-6.5

[ti-chi-bot]

@baurine: new pull request created to branch release-6.5: #7634.

In response to this:

/cherry-pick release-6.5

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 ti-community-infra/tichi repository.