fix(core): Include subpath type shims in published package

The `browser.d.ts` and `server.d.ts` root-level shims were missing from
the `files` list, so TypeScript compilers using `moduleResolution: "node"`
(which don't support the `exports` field) couldn't resolve
`@sentry/core/browser` or `@sentry/core/server` types. This broke
downstream consumers like `@sentry/react-native`.

Also adds `typesVersions` entries for the browser/server subpaths to
support TypeScript < 5.0.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: antonis

packages/core/browser.d.ts

@@ -0,0 +1,4 @@
+// This file is a compatibility shim for TypeScript compilers that do not
+// support the package.json `exports` field for resolving subpath exports.
+// Note: `typesVersions` in package.json may redirect this to the downleveled variant.
+export * from './build/types/browser';

packages/core/package.json

@@ -12,7 +12,9 @@
   "files": [
     "/build",
     "browser.js",
-    "server.js"
+    "browser.d.ts",
+    "server.js",
+    "server.d.ts"
   ],
   "main": "build/cjs/index.js",
   "module": "build/esm/index.js",
@@ -54,6 +56,12 @@
     "<5.0": {
       "build/types/index.d.ts": [
         "build/types-ts3.8/index.d.ts"
+      ],
+      "browser": [
+        "build/types-ts3.8/browser.d.ts"
+      ],
+      "server": [
+        "build/types-ts3.8/server.d.ts"
       ]
     }
   },

packages/core/server.d.ts

@@ -0,0 +1,4 @@
+// This file is a compatibility shim for TypeScript compilers that do not
+// support the package.json `exports` field for resolving subpath exports.
+// Note: `typesVersions` in package.json may redirect this to the downleveled variant.
+export * from './build/types/server';