🐛 fix(release): 改用 RELEASE_TOKEN 发布版本

- 工作流发布步骤改为显式使用仓库密钥 RELEASE_TOKEN
- 去掉发布脚本对 404 的吞错处理，改回明确暴露真实权限或接口错误
- 便于验证当前自定义 token 是否具备 Gitea Release 创建与附件上传权限

scripts/publish-gitea-release.sh

@@ -213,14 +213,6 @@ else
   create_result="$(api_post_json_with_status "$(api_url releases)" "$payload")" || fail "创建 Release 请求失败"
   create_status="${create_result##*$'\n'}"
   release_json="${create_result%$'\n'*}"
-  if [[ "$create_status" == "404" ]]; then
-    log "当前仓库不支持 Releases 或 Token 无 Release 权限，跳过发布"
-    printf '\n发布包已生成但未上传 Release：\n'
-    for package in "${PACKAGES[@]}"; do
-      printf '%s\n' "$package"
-    done
-    exit 0
-  fi
   [[ "$create_status" == "201" || "$create_status" == "200" ]] || fail "创建 Release 失败，HTTP 状态码：$create_status"
 fi