fix(ci): add node setup in release workflow

[devcrocod]

• Added setup-node with Node.js 22 to the release workflow — without it, TypeScript integration tests fail because the macOS runner has an incompatible pre-installed Node.js version

[Copilot]

Pull request overview

Updates the GitHub Actions Release workflow to ensure the release publishing job has a consistent Node.js environment and to streamline the workflow by removing an explicit Gradle build step.

Changes:

• Adds a actions/setup-node step (Node.js 22) to the release workflow.
• Removes the standalone ./gradlew build step and relies on publishToMavenCentral for compilation during publishing.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The PR title/description indicate this change is only about adding Node setup, but this workflow also changes the Gradle step from build to check and drops flags like --continue/--rerun-tasks/--max-workers. Please either update the PR description to reflect this behavioral change, or keep the step as build if the intent is to preserve the previous release validation semantics.