fix(ci): migrate macOS x64 release runner to macos-26-intel

[andya1lan]

改了什么 / What changed

• Replace the retired macos-13 runner used by the macOS x64 release job with macos-26-intel.
• Update the related comments while preserving the existing non-blocking x64 release behavior.

为什么 / Why

GitHub shut down the macOS 13 runner image on December 4, 2025:
https://github.blog/changelog/2025-09-19-github-actions-macos-13-runner-image-is-closing-down/

macos-26-intel is the current supported macOS 26 x64 runner label:
https://github.com/actions/runner-images#available-images

测试 / Testing

• Parsed .github/workflows/release.yml successfully with Ruby YAML.
• git diff --check passes.
• No application tests were run because this only changes the GitHub Actions runner image.

Checklist

• 代码风格和现有文件一致 / Code style matches existing files
• 没有引入 npm 依赖 / No new npm dependencies
• 不涉及 LS binary 协议 / LS binary protocol not affected
• 不涉及 dashboard UI / Dashboard UI not affected

[Copilot]

Pull request overview

This PR updates the GitHub Actions release workflow to keep the non-blocking macOS x64 build running on a supported Intel runner image, after the retirement of macos-13.

Changes:

• Switch the macOS x64 release job runner from macos-13 to macos-26-intel.
• Update surrounding workflow comments/step labels to reflect the new runner choice while preserving the existing non-blocking behavior.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[dwgx]

已合并 ✅ — v3.9.5

这条修的是我们自己的问题,而且我判断错了四次。

你指出 macos-13 已下线之后我去核实了终态:

v3.9.1 -> cancelled
v3.9.2 -> cancelled
v3.9.3 -> cancelled
v3.9.4 -> cancelled

全部是 cancelled,不是排队。 也就是连续四个版本都没有 macOS x64 二进制发出去。而我这边每次看到 GitHub UI 上的 queued,就照 workflow 里那条"x64 可能排几小时"的注释解释过去了,四次都判断成"非阻塞、不用管",从没查终态。

教训我记进交接文档了:注释解释的是设计意图,不是当前事实;判断某个 job "没问题"必须看终态。

核实过的依据:

• release.yml:151 确为 macos-13
• actions/runner-images README 确认 macos-26-intel 是当前 macOS 26 x64 标签
• 保留了 x64 不进 release needs 的非阻塞语义 ✅

台账:weight B+。四行改动,但价值全在诊断 —— 它纠正的是一个已经影响四个已发布版本的事实,而且是外部贡献者替维护方发现自身发布链缺口。这一条对标 lovivi #204 那种"十行精准方言修复"同档但更靠上。

谢谢,这个盯得比我细。