ci: publish GoReleaser drafts after artifact upload

[intel352]

Summary

• configure GoReleaser to keep GitHub releases as drafts while artifacts are uploaded
• publish the draft release only after the release workflow completes artifact/registry steps
• keep release workflows compatible with GitHub immutable releases

Verification

• actionlint on changed GoReleaser release workflow
• git diff --check

[Copilot]

Pull request overview

This PR updates the release process so GoReleaser creates GitHub releases as drafts first, then the workflow explicitly publishes the release after the GoReleaser job completes—supporting artifact upload sequencing and aligning with GitHub’s immutable release expectations.

Changes:

• Configure GoReleaser to create GitHub releases as drafts (release.draft: true).
• Add a workflow step that publishes the draft release by clearing the draft flag via gh release edit.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
.goreleaser.yaml	Sets GitHub releases to be created as drafts during GoReleaser execution.
.github/workflows/release.yml	Publishes the draft GitHub release at the end of the release job using the GitHub CLI.

---

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