[WIP] Update GitHub action workflow files

[Copilot]

• Analyzed all GitHub Actions workflow files in .github/workflows/
• Update actions/checkout@v2 → actions/checkout@v4 in all workflow files
• Update actions/setup-go@v3 → actions/setup-go@v5 in all workflow files
• Update actions/setup-node@v1 → actions/setup-node@v4 in docs_lint.yaml
• Update actions/setup-node@v3 → actions/setup-node@v4 in dm_ui_lint.yaml
• Add/update arm64 self-hosted runner configuration for arm64 builds
• Run code review and security checks

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Update the GitHub action workflow files</issue_title>
<issue_description>1. Update the action versions in action workflow files
2. Update to the correct GitHub self-hosted linux arm64 runner for building for arm64</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [release-8.5] Update the GitHub action workflow files #12542

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[ti-chi-bot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

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-sigs/prow repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

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]

Hi @Copilot. Thanks for your PR.

I'm waiting for a pingcap 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.

Details

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-sigs/prow repository.

[ti-chi-bot]

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/needs-linked-issue label, please provide the linked issue number on one line in the PR body, for example: Issue Number: close #123 or Issue Number: ref #456.

_{📖 For more info, you can check the "Contribute Code" section in the development guide.}