fix(ci): always run release cleanup on failure (#153)

The "Cleanup on failure" step in npm-publish.yml was gated on
`failure() && steps.create_release.outcome == 'success'`, so if
`gh release create` itself failed, cleanup was skipped and the bumped
commit/tag were left pushed with no npm/GitHub release. Drop the
create_release gate (`if: failure()`) and add `|| true` to the cleanup
commands so one missing artifact doesn't abort the rest.

Same fix as humanspeak/svelte-purify (CodeRabbit finding).

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Author: jaysin586

.github/workflows/npm-publish.yml

@@ -514,7 +514,7 @@ jobs:
                   pnpm publish --provenance --access public --no-git-checks
 
             - name: Cleanup on failure
-              if: failure() && steps.create_release.outcome == 'success'
+              if: failure()
               env:
                   RELEASE_VERSION: ${{ steps.version.outputs.new_version }}
                   GITHUB_TOKEN: ${{ secrets.ACTIONS_KEY }}
@@ -526,9 +526,9 @@ jobs:
                   fi
 
                   # Proceed with cleanup only if validation passes
-                  gh release delete "$RELEASE_VERSION" --yes
-                  git tag -d "$RELEASE_VERSION"
-                  git push --delete origin "$RELEASE_VERSION"
+                  gh release delete "$RELEASE_VERSION" --yes || true
+                  git tag -d "$RELEASE_VERSION" || true
+                  git push --delete origin "$RELEASE_VERSION" || true
 
             - name: Notify on failure
               if: failure()