fix(release): publish ink-compat by path

[RtlZeroMemory]

Summary

• publish @rezi-ui/ink-compat via package path (./packages/ink-compat) instead of workspace selector
• include packages/ink-compat in release version sync extras

Why

v0.1.0-alpha.43 failed in publish because root workspaces still omit ink-compat, so npm publish -w @rezi-ui/ink-compat cannot resolve. This keeps release working without changing workspace topology.

Summary by CodeRabbit

• Chores
  • Updated release workflow to properly include the ink-compat package in the publishing and versioning process.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f3c4215 and 12509c0.

📒 Files selected for processing (2)

• .github/workflows/release.yml
• scripts/release-set-version.mjs

---

📝 Walkthrough

Walkthrough

This PR updates the release configuration to include the ink-compat package. The workflow now publishes ink-compat from a local directory path instead of using workspace flags, and the version script includes ink-compat in the list of additional release package directories.

Changes

Cohort / File(s)	Summary
Release Configuration .github/workflows/release.yml, scripts/release-set-version.mjs	Updated ink-compat package publishing to use local path instead of workspace flag, and added ink-compat to the list of extra release package directories for version management.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 The ink-compat joins the release dance,
With local paths and a second chance,
No workspace flags will block the way,
Just hopping forward to release day! 🎉

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/release-inkcompat-publish

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}