SK-3004:Update common-release.yml for beta release.

[yaswanth-pula-skyflow]

Prevent beta releases from overwriting the latest/beta pointers

What changed

In .github/workflows/common-release.yml:

1. Disabled the "latest" tag deployment to S3 — commented out the Set Latest Tag, Deploy Latest Tag to S3, and Remove Latest Tag steps. Releases no longer push a latest file to the S3 bucket, so a beta release won't repoint the hosted CDN latest build.

2. Beta npm publish now uses a version-specific dist-tag — changed the beta publish from npm publish --tag beta to npm publish --tag v<RELEASE_VERSION>. Each beta is published under its own unique tag instead of overwriting the shared beta dist-tag.

Why

Previously every beta release overwrote the shared latest/beta pointers, meaning the newest beta always became the beta build consumers resolved to. This change keeps each beta isolated under its own version tag and stops betas from mutating the latest pointer, so publishing a new beta no longer clobbers the existing latest beta build.

Impact

• No functional change to public/internal release flows.
• Beta consumers must now install a specific v<version> tag rather than relying on a floating beta tag.

[github-actions]

✅ Gitleaks Findings: No secrets detected. Safe to proceed!

[github-actions]

Semgrep Findings: Issues with Error level severity are found (Error is Highest severity in Semgrep), Please resolve the issues before merging.