fix(ci): fix issue with nightly tag latest

[brandtkeller]

Description

Resolves the issue of goreleaser force push on the nightly tag making the latest tag resolve to nightly instead of the latest semver.

The Set CLI_VERSION step of the nightly release fetches the latest git tag and processes the semver to produce a mirror of what goreleaser is expecting (IE current latest semver + increment the patch integer). This was failing on the initial nightly releases after the nightly tag was the latest.

Example: https://github.com/zarf-dev/zarf/pkgs/container/packages%2Finit/518897335?tag=nightly0.0.1-nightly

This looks to be resolved as of the latest release v0.62.0 - but determined the problem to be with the latest tag. If we ignore any non-semver tags and preleases then this logic is more deterministic. This will aid other OpenSSF projects that might wish to have an example to pull from for this workflow.

Related Issue

Relates to #3928

Checklist before merging

• Test, docs, adr added or updated as needed
• Contributor Guide Steps followed

[netlify]

✅ Deploy Preview for zarf-docs canceled.

Name	Link
🔨 Latest commit	e940c97
🔍 Latest deploy log	https://app.netlify.com/projects/zarf-docs/deploys/68d6af0a38e63000083f4eb8

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[AustinAbro321]

@brandtkeller Could you explain further the problem that this PR solves or create an issue for it

[brandtkeller]

@AustinAbro321 Added to the description - this is a non-critical but minor fix to the logic with largely the aspiration to serve as an initial model for other golang OpenSSF projects to emulate.