chore(vscode): switch from npm to pnpm

[nhedger]

Summary

This PR:

• Replaces npm with pnpm for managing the dependencies of the VS Code extension.
• Adds the editors/vscode folder as a pnpm workspace

Additionally, this PR updates the package script so that vsce does not attempt to include node_modules in the VSIX file. This is required because at the moment vsce is not able to resolve dependencies downloaded by pnpm. This should not have any effect because we're already bundling the extension with all of its dependencies (--bundle is compile script).

Test Plan

• Run pnpm build
• Run pnpm package
• Run pnpm pack:dev
• Actually run extension and test formatting works

[ematipico]

Does vsce support pnpm now? The main reason we stayed at npm was because pnpm wasn't supported

microsoft/vscode-vsce#421

[nhedger]

Since we bundle the extension, it does not matter.

The reason vsce does not work with pnpm is that it cannot correctly resolve node_modules and include them in the VSIX file, which is not necessary in our case because the dependencies are bundled in the output file.

[ematipico]

@nhedger we need to update the workflows with pnpm

The release workflow is failing

https://github.com/biomejs/biome/actions/runs/6153342088/job/16697066155#step:13:1

[nhedger]

I can take a stab at it later today.

[nhedger]

@nhedger we need to update the workflows with pnpm

The release workflow is failing

biomejs/biome/actions/runs/6153342088/job/16697066155#step:13:1

#249

[lppedd]

The reason vsce does not work with pnpm is that it cannot correctly resolve node_modules and include them in the VSIX file, which is not necessary in our case because the dependencies are bundled in the output file.

@nhedger not sure if this was explained in the vsce repository discussion, but thanks!
This made it more clear on why and when we can bypass the issue.