Add a workflow_dispatch republish path for API clients

[ExtraToast]

What to build

A client can be regenerated and republished on demand, without a service release.

Today the publish workflow is callable only from a service's release pipeline, so any change to the generator configuration reaches consumers only after each service cuts a release — and then waits out Renovate's minimum release age. Add a manual dispatch path that regenerates and republishes a named service's clients at a bumped patch version, following the same pattern the project-board backfill workflow already uses.

This is sequenced after the plugin change only because both edit the same workflow; there is no logical dependency.

Acceptance criteria

• A client can be republished from a manual dispatch with no service release
• The dispatched path produces the same artifacts as the release path
• Republishing twice is safe
• Confirmed by reading the published package version, not by the run's status

Blocked by

• Emit TanStack Vue Query artifacts behind a subpath export