guard release workflow reruns

[cesaregarza]

Summary

• skip release-tag creation when the target tag already exists on origin
• skip GitHub release creation when the release already exists
• gate the release job on the publish path actually running successfully

Why

The push-to-main workflow was fragile on reruns and manual release intervention. If a tag or GitHub release already existed, rerunning the workflow could fail even when the repository state was otherwise fine. The release job also ran too loosely relative to the build-test-publish job.

Impact

Rerunning the workflow after a partial release or manual cleanup is now idempotent instead of erroring on duplicate tag/release creation.

Testing

• not run locally (GitHub Actions workflow change only)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud