fix: preserve workspace context for Rspack binding install - #71

Summary

Install @rspack/binding dependencies through the Rspack workspace instead of running an isolated install from crates/node_binding.

Rspack now uses pnpm catalog specifiers for the binding's development dependencies. The existing --ignore-workspace install cannot resolve those catalogs and, after it fails, leaves the shell in crates/node_binding, causing the later root build script to fail as a secondary error.

Using pnpm --filter @rspack/binding install --frozen-lockfile preserves workspace catalog resolution, keeps the working directory stable, and matches Rspack's current binding build workflow.

This is Rspack-specific because it is the only stack with a native binding preparation job. The action is consumed from this repository's main, so no action release or SHA pin update is required after merge.

Validation

• pnpm lint
• Against web-infra-dev/rspack@fe6890c7e11829a6459f1e9641b28aace4c0c268:
  • pnpm i --frozen-lockfile
  • pnpm --filter @rspack/binding install --frozen-lockfile
  • cargo codegen
  • pnpm run build:binding:release
• Full Ecosystem CI against web-infra-dev/rspack#14741: https://github.com/rstackjs/rstack-ecosystem-ci/actions/runs/30258401733
  • Prepare Rspack Binding succeeded and uploaded binding-linux-x64-gnu.
  • All ecosystem suites succeeded.

Related links

• Original failing binding preparation: https://github.com/rstackjs/rstack-ecosystem-ci/actions/runs/30248835010/job/89922236925