feat(android): drop Firebase analytics and crash reporting

Changelog: No more Firebase analytics or crash reporting

.agents/architecture.md

@@ -1147,22 +1147,6 @@ NDK version stands in for the hook's cache.
   `com.follow.clash.core.mobile.**`, the classes gobind's C glue looks up by name.
 - The CI `android` job compiles `:core` without Flutter, so it passes `-Ptarget-platform=android-arm64` to build one ABI.
 
-#### Android Crash Symbols
-
-Crashlytics NDK symbolicates a native crash only from libraries that still carry their symbols, and AGP strips every
-`.so` it packages, so the Android build keeps symbols until `:app`'s own strip step and the APK does not grow:
-
-- `bindCore` drops `-s` and `-w` from `go_ldflags`, and gomobile strips nothing itself; the desktop Cores stay
-  stripped because nothing consumes their symbols.
-- `:core` sets `packaging.jniLibs.keepDebugSymbols` so its own strip task leaves `libclash.so` intact on the way into
-  `:app`'s merged native libs, which is where the Crashlytics plugin reads it.
-- `:app` turns on `nativeSymbolUploadEnabled` and finalizes `assembleRelease` and `bundleRelease` with
-  `uploadCrashlyticsSymbolFileRelease` only when release signing is configured, the same condition that marks a real
-  release build; the checked-in `google-services.json` is a placeholder, so a local upload is noise at best, and CI
-  supplies both files together. The Crashlytics plugin wires the R8 mapping upload itself but leaves the native symbol
-  upload to the caller, so nothing else triggers it. `generateCrashlyticsSymbolFileRelease` runs `dump_syms` over the
-  Go Core for every ABI, which is the other reason it stays off for unsigned builds.
-
 ## Local Plugins
 
 - `setup`: build-time harness for Go core artifacts and the Rust helper, driven by a Dart build hook; no runtime Dart API.

.agents/rules.md

@@ -260,15 +260,10 @@ leaving a repo-wide policy as a comment reaches only the reader of that one file
   failure (user stop, low memory, signal, package change), never create one, and its timestamp is consumed through
   `handledExitAt` so the same exit cannot be counted twice.
 - `BootGuard` is an Android-only mechanism and gates itself: on every other platform `evaluate`, `markRunning` and
-  `markClosed` return without touching preferences. The desktop has neither of the two attribution sources — no
-  `ApplicationExitInfo` equivalent and no Crashlytics toggle — so a bare sentinel there would read a window closed on
-  the disclaimer dialog, or a session ended by shutdown, as a failed launch. Keep the platform check inside the guard;
-  callers in `bootstrap.dart` and `SystemAction` stay unconditional.
-- `FirebaseCrashlytics.didCrashOnPreviousExecution()` corroborates a failure and must not trigger one. Its marker file is
-  cleared by a background initialization that `dataCollectionArbiter` blocks while collection is disabled, which is the
-  default here, so one real crash makes it return true on every later launch. That latch is what made the app clear the
-  selected profile on every cold start; it is also why the probe is only read when `crashlytics` is enabled, keeping
-  Firebase uninitialized until the user consents.
+  `markClosed` return without touching preferences. The desktop has no `ApplicationExitInfo` equivalent to attribute an
+  exit, so a bare sentinel there would read a window closed on the disclaimer dialog, or a session ended by shutdown,
+  as a failed launch. Keep the platform check inside the guard; callers in `bootstrap.dart` and `SystemAction` stay
+  unconditional.
 - Recovery is graded: the first failed launch only skips `initStatus`, and `currentProfileId` is cleared only from
   `crashRecoveryClearThreshold` consecutive failures on. Do not let a single interrupted launch write to the config.
 - Desktop process ownership belongs to `DesktopCoreLifecycle`; do not start/kill `FlClashCore` from providers, widgets,