ci: route automatic publish to the npm-trusted workflow

[michaelfrog]

Problem

The automatic publish has been failing on every release. release.yml dispatched publish.yml ("Publish Package"), but publish.yml is not a configured npm OIDC trusted publisher, so npm publish died with ENEEDAUTH. The only workflow npm authorizes is publish-as-is.yml ("Publish public Package version") — the one that successfully shipped 0.0.4 manually.

A second symptom: the prs_created → next dispatch fired on every release-please PR open and also failed (same ENEEDAUTH), producing recurring red runs and no usable prerelease.

Fix (GitHub-side only — no npmjs changes)

• Point the on-release dispatch at publish-package-as-is so it triggers publish-as-is.yml, which npm already trusts. publish-as-is.yml publishes package.json's version as-is at latest — exactly what a merged release PR needs.
• Drop the broken next prerelease dispatch and gate the job on releases_created == 'true' only.
• Delete the orphaned publish.yml — it's no longer dispatched and was never an authorized publisher. publish-as-is.yml is now the sole publish path.

After this, merging a release-please PR auto-publishes to npm with no manual step.

Notes

• Do not rename publish-as-is.yml — npm's trusted-publisher match is keyed to the workflow filename.

Test plan

• Merge release PR chore(main): release 0.1.0 #20 (0.1.0) and confirm the publish-package-as-is dispatch runs and publishes 0.1.0 to npm latest.