fix: rename dist-tag v1 → v1-latest in v1-legacy release workflows

npm rejects dist-tags that are valid SemVer ranges. 'v1' parses as
>=1.0.0-0 <2.0.0-0. 'v1-latest' is not a SemVer range and is accepted.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: cs-raj

.github/workflows/release-production-core.yml

@@ -43,7 +43,7 @@ jobs:
         with:
           token: ${{ secrets.NPM_TOKEN }}
           package: ./packages/contentstack/package.json
-          tag: v1
+          tag: v1-latest
 
       - name: Create Core Production Release
         id: create_release

.github/workflows/release-production-platform-plugins.yml

@@ -43,28 +43,28 @@ jobs:
         with:
           token: ${{ secrets.NPM_TOKEN }}
           package: ./packages/contentstack-utilities/package.json
-          tag: v1
+          tag: v1-latest
 
       # Command
       - name: Publishing command (Production)
         uses: JS-DevTools/npm-publish@v3
         with:
           token: ${{ secrets.NPM_TOKEN }}
           package: ./packages/contentstack-command/package.json
-          tag: v1
+          tag: v1-latest
 
       # Config
       - name: Publishing config (Production)
         uses: JS-DevTools/npm-publish@v3
         with:
           token: ${{ secrets.NPM_TOKEN }}
           package: ./packages/contentstack-config/package.json
-          tag: v1
+          tag: v1-latest
 
       # Auth
       - name: Publishing auth (Production)
         uses: JS-DevTools/npm-publish@v3
         with:
           token: ${{ secrets.NPM_TOKEN }}
           package: ./packages/contentstack-auth/package.json
-          tag: v1
+          tag: v1-latest