feat: Expose crashed last run API

[antonis]

Problem Statement

Both native SDKs now provide APIs to check if the previous app session ended in a crash:

• iOS (Cocoa SDK 9.8.0+): SentrySDK.lastRunStatus — returns unknown, no-crash, or crash
• Android: Sentry.isCrashedLastRun() — returns a boolean

There is currently no way to access this information from the React Native (JavaScript) layer.

Use Cases

• Show a recovery UI (e.g., "Sorry, the app crashed") after restarting from a crash
• Disable experimental features that may have caused a crash
• Send custom analytics or breadcrumbs about crash recovery
• Implement progressive rollout logic that backs off after crashes

Proposed Solution

Expose a unified JS API, e.g.:

import * as Sentry from '@sentry/react-native';

const status = Sentry.lastRunStatus();
// Returns: 'unknown' | 'no-crash' | 'crash'

Implementation Notes

• Bridge SentrySDK.lastRunStatus on iOS and Sentry.isCrashedLastRun() on Android through the native modules
• Normalize the return value across platforms (iOS has 3 states, Android has a boolean — need to decide on a unified shape)
• Should be callable after Sentry.init()

References

• Cocoa SDK PR: feat: Add SentrySDK.lastRunStatus to distinguish unknown, no-crash and crash sentry-cocoa#7469
• Cocoa SDK bump to 9.8.0: chore(deps): update Cocoa SDK to v9.8.0 #5847

[linear-code]

RN-542

[antonis]

After looking into this, the added value over the existing crashedLastRun() API is minimal right now:

• iOS: sentry-cocoa 9.8.0 only exposes crashedLastRun as a BOOL, so we'd just be mapping true → "crash" and false → "no-crash". The "unknown" state would never be returned. The real 3-state lastRunStatus enum doesn't exist yet (tracked in feat: Add SentrySDK.lastRunStatus to distinguish unknown, no-crash and crash sentry-cocoa#7469).
• Android: Sentry.isCrashedLastRun() returns a nullable Boolean, so null → "unknown" is slightly richer, but that's the only practical gain.

Recommendation: Wait until sentry-cocoa ships a proper lastRunStatus API, then add lastRunStatus() as a replacement for crashedLastRun() in one shot — that way the new API actually provides meaningful new information on both platforms.