Wizard: surface an RN-specific JS-11 migration link when React Native adopts JS 11

[antonis]

Summary

Follow-up to #6774. While verifying that @sentry/wizard@8.0.0 doesn't break the React Native flow (RN stays on JS 10 for now), we found a gap to coordinate when RN moves to JS 11 in its next major.

Context

In @sentry/wizard v8, the shared helper printSdkV11MigrationGuideIfOutdated prints a v10→v11 migration link when it detects an already-installed SDK below v11. It picks the URL from a slug map, JS_SDK_V11_MIGRATION_GUIDE_SLUGS, which is keyed only to the seven JS-framework packages:

@sentry/angular, @sentry/cloudflare, @sentry/nextjs, @sentry/nuxt, @sentry/react-router, @sentry/remix, @sentry/sveltekit.

@sentry/react-native is not in that map, and the RN wizard flow doesn't call the helper at all today (correct while RN is on JS 10).

The gap

When the RN SDK bumps to JS 11 and the wizard starts installing/updating to that major, an RN user upgrading from an older SDK would either get no migration link or a fallback to the generic JS v10-to-v11 guide — not an RN-specific one.

Tasks (do when RN adopts JS 11)

• Decide whether RN needs a dedicated v10-to-v11 (JS-11) migration guide, or the generic JS guide is acceptable.
• If dedicated: add @sentry/react-native to JS_SDK_V11_MIGRATION_GUIDE_SLUGS in sentry-wizard and publish the RN migration doc.
• Wire the migration-guide / node-version-warning behavior into the RN wizard flow only once RN is actually on JS 11 (so it doesn't fire prematurely).

Note

The actual code change lives in getsentry/sentry-wizard, not this repo. This issue tracks the RN-side coordination for the JS-11 next major.

References

• Verification context: Test with sentry-wizard v8.0.0 (new major) for breaking changes #6774
• JS v10→v11 migration guide: https://docs.sentry.io/platforms/javascript/migration/v10-to-v11/

[linear-code]

RN-795

[antonis]

⚠️ Noting that this might not be needed due to #6770