fix release workflow trigger

[fqjony]

Summary

• Remove branch filter from release workflow — the reusable workflow gates on release_branch internally (matches udx/worker-deployment pattern)
• Add workflow_dispatch for manual re-triggers

Previous runs failed with ENEEDAUTH because re-runs inherited stale permissions from before the GitHub environment was created. A fresh push to main will pick up the correct id-token: write permission.

Test plan

• Merge triggers fresh release run with OIDC npm publish

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Updates the npm release GitHub Actions workflow triggers so releases can be re-run manually and are no longer limited by a main branch filter (relying on the reusable workflow’s internal release_branch gating).

Changes:

• Removed the push.branches: [main] filter so the workflow triggers on any push.
• Added workflow_dispatch to allow manual runs/re-triggers.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

on: push: is currently configured with a null/empty value. While GitHub Actions often treats this like an unfiltered push trigger, it’s ambiguous and easy to misread. Consider making it explicit (e.g., push: {} or using the short form on: [push, workflow_dispatch]) to avoid YAML/Actions parsing surprises and improve clarity.

Suggested change

	push:
	push: {}