feat(tibuild): support commit to build

[wuhuizuo]

Usage:

/devbuild trigger --engine tekton -e enterprise tidb v8.5.0-dev commit/

Signed-off-by: wuhuizuo wuhuizuo@126.com

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.

Key changes in the pull request:

• Added support for building from a specific commit using a new command devbuild trigger --engine tekton -e enterprise tidb v8.5.0-dev commit/<sha>
• Created a new function getBranchForCommit to retrieve the branch name for a specific commit from Github
• Added an implementation for GetBranchesForCommit in GitHubClient

Potential problems:

• None that I can see at the moment

Fixing suggestions:

• The code looks good, but it would be helpful to add some unit tests for the new functionality to ensure everything is working as expected.

[wuhuizuo]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wuhuizuo

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:

• tibuild/OWNERS [wuhuizuo]

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]

I have already done a preliminary review for you, and I hope to help you do a better job.

Summary of changes:

This pull request adds a new feature to the tibuild package which now supports building from a specific commit. It also adds a new function GetBranchesForCommit to the GHClient interface to retrieve the branches that contain the specified commit.

Potential problems:

• The new feature may introduce additional complexity to the system and may require additional testing.
• The GetBranchesForCommit function in gh_client.go may not work as expected because it uses a URL that does not appear to be documented in the GitHub API.

Fixing suggestions:

• Consider adding additional tests to ensure that the new feature works as expected and does not introduce any regressions.
• Consider using the GitHub API to retrieve the branches that contain the specified commit instead of using a URL that may not be documented in the API. This will ensure that the function works as expected and is less likely to break in the future.