fix(telemetry): upgrade Sentry SDK to 10.39.0 and remove custom patches (#249)

## Summary

Upgrade `@sentry/bun` and `@sentry/node` from 10.38.0 → 10.39.0 and
remove all custom patches/workarounds that are now fixed upstream.

## Changes

- **Removed `patches/@sentry%2Fcore@10.38.0.patch`** (92 lines) — Added
`.unref()` to timers in `setupWeightBasedFlushing`,
`_isClientDoneProcessing`, and `makePromiseBuffer` to prevent the CLI
from hanging on exit. Fixed upstream by
[#19062](getsentry/sentry-javascript#19062) and
[#19174](getsentry/sentry-javascript#19174).
- **Removed runtime context workaround in `src/lib/telemetry.ts`** (14
lines) — Manually overrode `options.runtime` after `Sentry.init()` to
report Bun instead of Node.js. Fixed upstream — `NodeClient` now uses
`options.runtime || { name: 'node', ... }` and `@sentry/bun` passes `{
name: 'bun', version: Bun.version }`. Tracked as
[#19269](getsentry/sentry-javascript#19269).
- **Updated `package.json`** — Bumped both SDK packages to `10.39.0` and
removed `@sentry/core` from `patchedDependencies`.

## Verification

- Verified all three upstream fixes by reading the 10.39.0 source code
and linked PRs
- `bun install`, typecheck, lint, and tests all pass cleanly
- No new test failures introduced (pre-existing ~95 failures on `main`
are unrelated)

Author: BYK

bun.lock

@@ -28,9 +28,9 @@
   "devDependencies": {
     "@biomejs/biome": "2.3.8",
     "@sentry/api": "^0.1.0",
-    "@sentry/bun": "10.38.0",
+    "@sentry/bun": "10.39.0",
     "@sentry/esbuild-plugin": "^2.23.0",
-    "@sentry/node": "10.38.0",
+    "@sentry/node": "10.39.0",
     "@stricli/auto-complete": "^1.2.4",
     "@stricli/core": "^1.2.4",
     "@types/bun": "latest",
@@ -62,7 +62,6 @@
   },
   "packageManager": "bun@1.3.9",
   "patchedDependencies": {
-    "@stricli/core@1.2.5": "patches/@stricli%2Fcore@1.2.5.patch",
-    "@sentry/core@10.38.0": "patches/@sentry%2Fcore@10.38.0.patch"
+    "@stricli/core@1.2.5": "patches/@stricli%2Fcore@1.2.5.patch"
   }
 }

package.json

@@ -214,21 +214,6 @@ export function initSentry(enabled: boolean): Sentry.BunClient | undefined {
     const isBun = typeof process.versions.bun !== "undefined";
     const runtime = isBun ? "bun" : "node";
 
-    // Fix runtime context: @sentry/bun v10 delegates to @sentry/node's NodeClient,
-    // which always overrides runtime to { name: 'node', version: process.version }.
-    // Under Bun, process.version returns the Node.js compat version (e.g. v24.3.0),
-    // not the Bun version. Override it so event.contexts.runtime is correct and
-    // Sentry's server-side tag promotion creates an accurate 'runtime' tag.
-    // TODO: Remove once fixed upstream: https://github.com/getsentry/sentry-javascript/issues/19269
-    if (isBun) {
-      // biome-ignore lint/suspicious/noExplicitAny: accessing internal SDK option not exposed in NodeClientOptions
-      const options = client.getOptions() as any;
-      options.runtime = {
-        name: "bun",
-        version: process.versions.bun as string,
-      };
-    }
-
     // Tag whether running as bun binary or node (npm package).
     // Kept alongside the SDK's promoted 'runtime' tag for explicit signaling
     // and backward compatibility with existing dashboards/alerts.