chore(CI): use new release workflow

[chenjiahan]

Summary

The new release workflow is the same as Rsbuild and Rspress, see https://github.com/web-infra-dev/rsbuild/blob/main/.github/workflows/release.yml.

GITHUB_TOKEN is no longer required in this workflow.

bench-pr.yml is deleted. We can add it back if it still need to be used.

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[fi3ework]

Based on web-infra-dev/rsbuild@058993d, is there a need to restrict the "latest" dist-tag to only trigger on the main branch? This would prevent packages from being published before a PR is merged, meaning that publishing an npm package would require review by others to prevent accidental publishing.

[codspeed-hq]

CodSpeed Performance Report

Merging #592 will not alter performance

_{Comparing release_workflow_1223 (3c813cf) with main (ac486b9)}

Summary

✅ 5 untouched benchmarks

[fi3ework]

Based on web-infra-dev/rsbuild@058993d, is there a need to restrict the "latest" dist-tag to only trigger on the main branch? This would prevent packages from being published before a PR is merged, meaning that publishing an npm package would require review by others to prevent accidental publishing.

Because other PRs may be merged after the merge and before the release, we cannot guarantee that the commit being released is the final release commit. We can adjust our approach in the future based on the situation.