feat(react-router): Align options with shared build time options type

[s1gr1d]

closes #17066

Also updates the shared BuildTimeOptionsBase type a bit to align with the latest changes.

[github-actions]

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario	Requests/s	% of Baseline	Prev. Requests/s	Change %
GET Baseline	9,290	-	9,386	-1%
GET With Sentry	1,420	15%	1,413	+0%
GET With Sentry (error only)	6,180	67%	6,155	+0%
POST Baseline	1,197	-	1,210	-1%
POST With Sentry	527	44%	528	-0%
POST With Sentry (error only)	1,080	90%	1,079	+0%
MYSQL Baseline	3,308	-	3,351	-1%
MYSQL With Sentry	502	15%	490	+2%
MYSQL With Sentry (error only)	2,770	84%	2,751	+1%

View base workflow run

[s1gr1d]

The changes in this file are basically just a back-port of the changes in the bundler-plugin type.

getsentry/sentry-javascript-bundler-plugins@main/packages/bundler-plugin-core/src/types.ts

[chargome]

Looks good!

[chargome]

q: Why is this awaited?

[s1gr1d]

As this can be a Promise when coming from the unstable_... option: getsentry/sentry-javascript-bundler-plugins@4255012

[JPeer264]

I am a little late to the party. I leave this here for the record

[JPeer264]

l: following would do the same and is a little shorter

Suggested change

	disable: sourceMapsUploadOptions?.enabled === false ? true : sentryConfig.sourcemaps?.disable,
	disable: sourceMapsUploadOptions?.enabled === false || sentryConfig.sourcemaps?.disable,

[JPeer264]

l: you could use new SentryCore.SentryNonRecordingSpan({ traceId: '1', spanId: '2' }) instead, then you can get rid of the ts-expect-error. But for that you need too adapt the mocking:

vi.mock('@sentry/core', async (importOriginal) => {
  return {
    ...(await importOriginal()),
    getActiveSpan: vi.fn(),
    ...
  };
});