sentryBunPlugin should inject debug IDs and upload source maps, like the esbuild plugin #25618

Problem Statement

The Bun guide recommends building with sentryBunPlugin from @sentry/bun/plugin, and we do (Bun 1.4.3, @sentry/bun 11.8.0) so pg queries become db spans. But that plugin only runs the orchestrion transform (@sentry/server-utils/orchestrion/bundler/bun.js). Getting readable server stack traces takes a second tool: build with sourcemap: "external", then sentry sourcemap inject and sentry sourcemap upload, plus setting the release ourselves. Without that, errors show frames like dist/index.js:169867 with js_no_source.

The Bun source maps page lists webpack, Rollup, Vite and esbuild under "Sentry Bundler Support", but not Bun, even though Bun is now the bundler the Bun guide tells you to use. The legacy sentry-cli that older docs point to silently skips Bun output (Bun writes its own //# debugId), so the manual path is easy to get wrong.

Solution Brainstorm

Let sentryBunPlugin take the same build options as sentryEsbuildPlugin (org, project, authToken, sourcemaps, release) and, when an auth token is present, inject the debug ID snippet (reusing the ID Bun already emits) and upload the maps at the end of Bun.build. Then add Bun to "Sentry Bundler Support" on the source maps page.

Additional Context

Minimal build:

import { sentryBunPlugin } from "@sentry/bun/plugin";

await Bun.build({
  entrypoints: ["./src/index.ts"],
  outdir: "./dist",
  target: "bun",
  sourcemap: "external",
  plugins: [sentryBunPlugin()],
});

Related: #19707 (Improve Bun Support), getsentry/toolkit#1513 (CLI side of Bun debug IDs, fixed in getsentry/toolkit#1515).

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}