feat(mobile): optional crash reporting

[brow]

What changed?

Adds default-on Sentry crash reporting to Buzz mobile with an explicit opt-out.

Reporting initializes only in builds that inject a Sentry key at build time (e.g. our app store builds) and stops immediately when the preference is revoked.

The SDK is configured to omit default PII, screenshots, view hierarchy, replay, tracing, logs, breadcrumbs, request bodies, and user text.

Native Android auto-init providers are removed so no SDK code runs before Dart applies consent.

The change will be inactive until our release build pipeline is updated to inject the Sentry key.

How is it tested?

Added tests:

• DiagnosticsController
• SentryConfig
• SettingsPage

Flutter analysis and the full mobile test suite pass.

Before / After

Before	After

[brow]

@codex review

[brow]

@builderbot review

[chatgpt-codex-connector]

To use Codex here, create a Codex account and connect to github.

[brow]

🤖 Review summary: I found one blocking startup issue and one dependency compatibility concern on fb375ddf. Sentry initialization must not prevent runApp() when persisted consent is present, and the resolver changes should be acknowledged because Sentry 9.24.0 explicitly pins jni 0.14.2. Details are in the inline review comments. I did not approve this head.