chore: allow dependencies to be built with pnpm v10

[odockal]

What does this PR do?

Explicitly state the dependencies with build scripts to execute during ie. install lifecycle phase in pnpm v10. This will enable to e2e tests to run.

We have alternatives, I went with the minimal working solution, other options:

"onlyBuiltDependencies": ["electron", "@biomejs/biome", "esbuild", "svelte-preprocess"] -> building those that appeared on the warning
OR
"neverBuiltDependencies": [] -> to build any

When I run pnpm approve-builds locally, it updated pnpm-workspace.yaml file instead of package.json.

Screenshot / video of UI

What issues does this PR fix or reference?

#1447

How to test this PR?

E2E tests should be passing now.

[benoitf]

electron should not be a 'known' dependency from the extension pov

[odockal]

Until it is resolved in the core Refactor the type of dependency for electron tests-playwright package, we cannot do much in the PR now.

[benoitf]

@odockal

well you could add

If you want the old pre v10 behaviour, so you want to allow all dependencies to run postinstall scripts, then add this to your package.json:

{
  "pnpm": {
    "neverBuiltDependencies": []
  }
}

and it'll be like pnpm 9.x

[jeffmaury]

Seems unrelated

[odockal]

@odockal

well you could add

If you want the old pre v10 behaviour, so you want to allow all dependencies to run postinstall scripts, then add this to your package.json:

{
  "pnpm": {
    "neverBuiltDependencies": []
  }
}

and it'll be like pnpm 9.x

@benoitf sry, missed this comment.

@jeffmaury @deboer-tim Now it should be in a shape for review.