Emit TanStack Vue Query artifacts behind a subpath export

[ExtraToast]

What to build

The shared client publisher emits TanStack Vue Query artifacts, so every published TypeScript client exposes ready-made query and mutation options whose cache keys derive from operation ids.

Add the @tanstack/vue-query plugin to the generator configuration the publish action writes, with query options and mutation options both enabled. Expose the generated file behind its own subpath export and declare @tanstack/vue-query as a peer dependency, so a consumer that is not a Vue application never resolves it. The generator and validator versions are already pinned centrally in the action — pin this one the same way.

Acceptance criteria

• A generated client exposes query and mutation options for every operation
• The framework-free entrypoint still resolves with no TanStack Query installed
• The TanStack Query version is pinned in the action, not floated
• Verified by pulling the published package and reading its contents, not by a green workflow run

Blocked by

None — can start immediately.