fix(release): publish ink-compat and shim packages

[RtlZeroMemory]

Summary

• publish @rezi-ui/ink-compat in release workflow
• publish ink-gradient-shim and ink-spinner-shim in release workflow
• include shim package directories in release-set-version so each release tag bumps their versions before publish

Why

v0.1.0-alpha.41 only published core/native/testkit/node/jsx/create-rezi. This wires missing packages into the same release pipeline so npm stays in sync.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b8eb530257

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Remove publish steps that target non-existent packages

npm publish --help defines -w|--workspace <workspace-name>, and in this commit the new command npm publish -w @rezi-ui/ink-compat fails with No workspaces found because the root package.json workspace list has no @rezi-ui/ink-compat; the adjacent shim publishes also fail (ENOENT) because packages/ink-gradient-shim and packages/ink-spinner-shim are not present in this tree. On any v* tag, the release workflow now aborts during publish, so no release can complete.

Useful? React with 👍 / 👎.