fix: make release workflow idempotent and reset version to last successful release

[dzole0311]

Related Ticket: #1907

Description of Changes

Opening a draft PR to attempt to fix the broken release workflow:

• Reset package.json version to 6.16.0, the last successful published version to realign with npm and GitHub release history
• Added cleanup step to the release workflow to automatically remove stale Git tags left by failed runs. Can't easily test this until we merge / publish

Notes & Questions About Changes

• This resolves the npm error Version not changed issue caused by leftover tags (v6.17.0+)
• After merge, the next workflow run should bump to v6.17.0 and publish cleanly
• Manually ran git tag -d v6.17.0 v6.18.0 v6.19.0 v6.19.1 and git push origin :refs/tags/...` to delete stale tags locally and on GitHub
• Old draft releases in the veda-ui github repository (v6.17.0–v6.19.1) should be deleted manually. I think we can already do that, before the next publish attempt? cc @vgeorge @snmln

Validation / Testing

• Verified locally that stale tags were deleted (git fetch --tags --prune shows latest as v6.16.0)
• After merging, manually trigger "Release Every Monday" workflow and confirm it completes the release and creates new tag v6.17.0.

[netlify]

✅ Deploy Preview for veda-ui ready!

Name	Link
🔨 Latest commit	ac39112
🔍 Latest deploy log	https://app.netlify.com/projects/veda-ui/deploys/6911bda3d0ce5e00081d6c67
😎 Deploy Preview	https://deploy-preview-1908--veda-ui.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[vgeorge]

@dzole0311 I removed the draft releases after v6.16.0. It is a good idea to clean things up before releasing. Let merge and check if it works. It would be nice to have a cleanup step when the npm token fails, because release-it generates tags/drafts before the npm publish. We can address that in a separate PR.