chore(publish): Use workspaces option in Craft NPM target

[Lms24]

Makes use of craft's new feature to detect npm packages in topological order. This makes our publishing process slightly more robust since previously, we didn't specify an explicit order. This is also a trial run for the sentry-javascript repo, so that we can test the craft option on a smaller monorepo like this one.

> volta run --node 20.18.2 npx @sentry/craft@latest targets
[info] Discovered 6 publishable yarn workspace packages
[
    "github",
    "npm[@sentry/babel-plugin-component-annotate]",
    "npm[@sentry/bundler-plugin-core]",
    "npm[@sentry/webpack-plugin]",
    "npm[@sentry/vite-plugin]",
    "npm[@sentry/rollup-plugin]",
    "npm[@sentry/esbuild-plugin]"
]

[github-actions]

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

This PR will not appear in the changelog.

---

_{🤖 This preview updates automatically when you update the PR.}

[andreiborza]

dumb question: do we then still need includeNames and the tarballs specified in requireNames?

[Lms24]

dumb question: do we then still need includeNames and the tarballs specified in requireNames?

Good question, I'm not sure actually! @BYK can we remove them safely? I think it doesn't hurt having them but if they're no longer necessary, happy to remove them.

[BYK]

You'd probably need requireNames to be set as it is the artifact provider config and npm target cannot (and should not) influence that setting.

includeNames should be set automatically here: https://github.com/getsentry/craft/blob/abd8cd1fe1f3bdca1fc8e9d9dafa2bad5d5fd665/src/targets/npm.ts#L209-L219