feat(core): Add applicationKey to BuildTimeOptionsBase

[chargome]

Adds a top-level applicationKey option to the shared BuildTimeOptionsBase interface, so users can configure thirdPartyErrorFilterIntegration without needing unstable_* escape hatches.

Wires up forwarding in:

• React Router
• SvelteKit
• Astro
• Nuxt

Will do Next.js in a follow up as this does not implement the interface

closes #17384

[nicohrubec]

the tanstack start sdk uses this type as well, should probably be wired in there too?

[nicohrubec]

lgtm

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 57ac005. Configure here.}

[cursor]

Missing integration or E2E test for new feature

Low Severity

This is a feat PR but only includes unit tests. Per the project review rules, feat PRs need at least one integration or E2E test. While the unit tests verify applicationKey option forwarding to the vite plugin, there's no integration or E2E test confirming the thirdPartyErrorFilterIntegration actually works end-to-end with the new top-level option in any of the wired-up frameworks.

Additional Locations (2)

• packages/react-router/test/vite/makeCustomSentryVitePlugins.test.ts#L50-L61
• packages/nuxt/test/vite/sourceMaps.test.ts#L233-L244

 

^{Triggered by project rule: PR Review Guidelines for Cursor Bot}

^{Reviewed by Cursor Bugbot for commit 57ac005. Configure here.}