build: upgrade pnpm to v10

[siketyan]

Summary

This pull request upgrades pnpm to v10 (latest).
I don't know why this is not yet achieved by Renovate.

Test Plan

Existing CIs for Node.js should pass.

[arendjr]

LGTM, but it does appear changes to the package.json don't trigger the right CI jobs, so that might be something we want to look into.

[ematipico]

I don't know why this is not yet achieved by Renovate.

I believe we disallow major upgrades, but I might be wrong

[siketyan]

@arendjr
We have two workflows triggered by pull_request trigger:

• pull_request.yml: When Rust or Cargo files changed
• pull_request_js.yml: When JS/TS files changed

Currently we run Node.js API tests in pull_request.yml, so this PR doesn't trigger it. However I think we should run tests for Node.js APIs when either Rust files or JS/TS files are changed. Maybe we should introduce a new workflow pull_request_node.yml or something to trigger by both files?

[siketyan]

@ematipico
I don't see any configuration that disables major upgrades: https://github.com/biomejs/biome/blob/d40bf1f63715156dcfd727bfb4a71e56eb934c40/.github/renovate.json

I checked https://developer.mend.io/github/biomejs/biome and pnpm is on the list, but there is a long awaiting queue 😓

[arendjr]

I think we should run tests for Node.js APIs when either Rust files or JS/TS files are changed. Maybe we should introduce a new workflow pull_request_node.yml or something to trigger by both files?

This makes sense to me, yes.

But I meant that it seems a mistake that pull_request_js.yml isn't triggered when package.json changes, as in this PR.

[siketyan]

But I meant that it seems a mistake that pull_request_js.yml isn't triggered when package.json changes, as in this PR.

Yeah, that is also a problem. I will create a new PR to resolve these before merging this one.