ci: replace unmaintained github-tag-action with plain git tag/push

[mikeland73]

Summary

The edge release job only used mathieudutour/github-tag-action to create and push a pre-computed tag (EDGE_TAG), not its semver auto-bump feature. That action is unmaintained (last release Mar 2024) and runs on the soon-to-be-deprecated Node 20, so this replaces it with two plain git commands that do exactly what was being used. The existing contents: write permission and default GITHUB_TOKEN from checkout cover pushing the tag, and the step's outputs weren't referenced elsewhere.

How was it tested?

Static review of the workflow — the change is a no-op on behavior, swapping the action for the equivalent git tag/git push it was performing. The full edge release path runs on the weekly schedule / manual dispatch.

Community Contribution License

All community contributions in this pull request are licensed to the project
maintainers under the terms of the
Apache 2 License.

By creating this pull request, I represent that I have the right to license the
contributions to the project maintainers under the Apache 2 License as stated in
the
Community Contribution License.

[Copilot]

Pull request overview

This PR updates the CLI release GitHub Actions workflow to stop using the unmaintained mathieudutour/github-tag-action and instead create/push the precomputed edge tag using plain git, keeping the edge release flow functionally equivalent while removing the action dependency.

Changes:

• Remove mathieudutour/github-tag-action usage for edge tag creation.
• Add direct git tag + git push commands to create and push EDGE_TAG.

---

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

[mikeland73]

Good call — made the step idempotent in 0ddcaf1. git tag -f plus git push -f origin refs/tags/$EDGE_TAG so a same-day rerun overwrites the existing tag instead of failing, and the explicit refs/tags/ ref removes the ambiguity.