feat: decouple pnpmBuildDependency from sv (2)

[jycouet]

Closes #1030

Description

replacing

run: ({ sv }) => {
  sv.pnpmBuildDependency('my-native-dep');
}

by

import { pnpm } from '@sveltejs/sv-utils';

run: ({ sv, packageManager }) => {
  if (packageManager === 'pnpm') {
    sv.file(file.findUp('pnpm-workspace.yaml'), pnpm.onlyBuiltDependencies('my-native-dep'));
  }
}

DX is not the best, but sv is less dependant of pnpm & changes.

Alternative:
rename: sv.pnpmBuildDependency('my-native-dep'); to sv.pnpmOnlyBuiltDependencies('my-native-dep'); to be explicit (but still coupled).

@benmccann WDYT?

Checklist

• Update snapshots (if applicable)
• Add a changeset (if applicable)
• Allow maintainers to edit this PR
• I care about what I'm doing, no matter the tool I use (Notepad, Sublime, VSCode, AI...)

[changeset-bot]

🦋 Changeset detected

Latest commit: 0ca761e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
sv	Minor
@sveltejs/sv-utils	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

Open in StackBlitz

npx https://pkg.pr.new/svelte-migrate@1037

npx https://pkg.pr.new/sv@1037

npx https://pkg.pr.new/@sveltejs/sv-utils@1037

commit: 0ca761e

[svelte-docs-bot]

Preview: https://svelte-dev-git-preview-cli-1037-svelte.vercel.app/

[benmccann]

nice! I like it!