chore(sync): add structured recovery telemetry

[MohamadJaara]

Summary

• add structured app-lifecycle telemetry for foreground and push-triggered sync requests
• use typed event, trigger, and outcome enums to keep dashboard field values stable
• emit a shared schemaVersion / event / component envelope and omit null fields
• pin the app telemetry wire format with a regression test
• update Kalium to chore(sync): add structured recovery telemetry kalium#4311 for structured executor, retry, and network telemetry

Why

The reconnect recovery in the base PR needs an observable path from app foregrounding or push handling through Kalium retry execution. Previously the app emitted prose logs that could not be reliably joined with SDK retry and network events.

Stack

• stacked on fix(sync): recover after connectivity returns #5069 (mo/fix/sync-retry-after-no-internet)
• depends on chore(sync): add structured recovery telemetry kalium#4311, which is itself stacked on the Kalium recovery PR fix: message bubble reply accent background #4310

This PR contains telemetry changes only.

Validation

• AppSyncTelemetryTest
• SyncLifecycleManagerTest
• app static code analysis / Detekt
• Kalium logic JVM tests, Android network host tests, and Kalium Detekt in the dependency PR