Centralize release publication dispatches

Problem

The release process mixes explicit workflow dispatches with release: published listeners. Releases created using GITHUB_TOKEN do not trigger downstream workflows, so v1.45.0 skipped both TypeScript registry publishers. The PyPI publisher also failed because its release version was not propagated between steps.

Acceptance criteria

• Make create-release.yml the sole release-publication orchestrator.
• Explicitly dispatch PyPI, npm, GitHub Packages, server-image, and binary workflows.
• Make registry publishers dispatch-only and require a version input.
• Execute current publisher definitions while publishing immutable tagged sources.
• Preserve manual, independently retryable recovery workflows.
• Remove redundant release/tag publication triggers and update operator documentation.

This issue was created by an AI agent (OpenHands) on behalf of Graham Neubig.

Start with create-release.yml and trace the existing release: published listeners and publisher workflow definitions. Verify how the PyPI version currently moves between steps, then make the named publication workflows dispatch-only with explicit version inputs. Done means all listed publishers are dispatched by create-release.yml, tagged sources remain immutable, manual recovery still works, redundant triggers are removed, and operator documentation is updated.