chore(ci): treat any non-prod dist-tag as canary in publish workflow

The publish workflow had `inputs.dist-tag == 'next'` gates on the bump,
commit, and `pnpm publish:next` steps. v4 passes `dist-tag: 'v4'`, which
silently skipped all four steps — the workflow reported success but
nothing was published.

Switching to `!= 'prod'` lets any canary tag (`next`, `v4`, future
release lines) flow through. The actual npm dist-tag is still set per
branch by the `publish:next` script (`--dist-tag next` on master,
`--dist-tag v4` on v4).

Author: B4nan

.github/workflows/publish-to-npm.yml

@@ -64,12 +64,12 @@ jobs:
               run: pnpm ci:build
 
             - name: Bump canary versions
-              if: inputs.dist-tag == 'next'
+              if: inputs.dist-tag != 'prod'
               run: |
                     pnpm turbo copy --force -- --canary=major --preid=beta
 
             - name: Commit changes
-              if: inputs.dist-tag == 'next'
+              if: inputs.dist-tag != 'prod'
               uses: EndBug/add-and-commit@v10
               id: commit
               with:
@@ -90,7 +90,7 @@ jobs:
                   GH_TOKEN: ${{ secrets.APIFY_SERVICE_ACCOUNT_GITHUB_TOKEN }}
 
             - name: Publish to NPM (@next)
-              if: inputs.dist-tag == 'next'
+              if: inputs.dist-tag != 'prod'
               uses: nick-fields/retry@v4
               with:
                   timeout_minutes: 10