ci(release): publish beta releases to npm latest dist-tag

Set the beta branch channel to false so beta releases publish to the npm `latest` dist-tag (default channel) instead of a `beta` dist-tag. The tag is applied during `npm publish`, so it works with OIDC trusted publishing (no NPM_TOKEN).

Existing 1.1.0-beta.* tag git notes were migrated to include the default channel so the version counter keeps incrementing after the switch (otherwise getLastRelease finds no match and the version resets).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: saeedjamshaid

release.config.cjs

@@ -8,7 +8,14 @@ module.exports = {
     },
     {
       name: "beta",
-      prerelease: true
+      prerelease: true,
+      // Publish beta releases to the npm `latest` dist-tag (the default channel)
+      // rather than a `beta` dist-tag, so `npm install @apimatic/cli` resolves to
+      // the current beta. The dist-tag is applied during `npm publish`, so this
+      // works with OIDC trusted publishing (no NPM_TOKEN needed).
+      // NOTE: existing beta tags' git notes were migrated to include the default
+      // channel so version continuity is preserved (beta.N keeps incrementing).
+      channel: false
     }
   ],
   plugins: [