feat(analytics): add group chat events and send them from Android

[bmc08gt]

Group chats sent no analytics beyond the chat events they share with DMs. This adds a Group domain to events.toml (generating GroupEvents), Chat Muted and Chat Unmuted in the Chat domain, and fires all of them from Android.

iOS needs a flipcash-shared-core-spm release after this merges before it can send these events. The Swift typealiases for GroupEvents and the new lists are in AnalyticsEvents.swift.

Catalogue

Event	Properties
Group: New Opened	none
Group: Created	State, Error?, Gate Mint?, Has Picture
Group: Edited	Field (Name, Picture), State, Error?
Group: Invite Sheet Opened	Source (Chat, Profile), Member Count
Group: Invite Shared	Method (Share, Copy)
Group: Invite Followed	Source (Link, QR, Chat Card)
Group: Gate Shown	Access (Eligible, Blocked), Gate Mint?, Member Count
Group: Gate Funding Tapped	Method (Buy Token, Add Cash), Gate Mint?
Group: Joined	State, Error?, Member Count, Gated
Group: Left	State, Error?, Member Count
Group: Info Opened	Member Count, Is Member
Chat Muted	Chat Type, Duration, State, Error?
Chat Unmuted	Chat Type, State, Error?

• MuteDuration: 1 Hour, 8 Hours, 1 Week, Always. Android's MuteState and iOS's MuteChatSheet offer the same four.
• Error: the RPC's result name from the proto (Denied, NotFound, RulesNotSatisfied, TitleModerated, …), or Network for a transport failure. Throwable.chatResult in Conversions.kt does the mapping. It also returns Validation when a request fails proto validation before it is sent, since there is no server result to name.
• Gate Mint: left out when the group has no token gate, including a rule that any currency satisfies.
• Member Count: the roster the screen held before the action.
• Drift: TokenInfoSource.CHAT_GATE notes that iOS doesn't send it. Its gate buy button pushes the buy screen and never opens Token Info. Group: Gate Funding Tapped covers that tap on both apps.

Android call sites

• New Opened and Created: NewChatScreen and CreateGroupViewModel.create().
• Edited: EditGroupNameViewModel and EditGroupPictureViewModel.
• Muted and Unmuted: MuteChatViewModel only had the chat id. AppRoute.MuteChat now carries the ChatType, and ConversationReference gains chatType so the chat list can say what kind of DM it is instead of only isGroup. The sheet passes up the MuteOption rather than the MuteState built from it, so the picked duration is still known when the event fires.
• Gate, invite, join, leave, info: ChatViewModel. The screens dispatch the taps as events, so the count and mint come from the group the view model holds. Gate Shown is taken once per view model, which the chat flow scopes to one visit, so a balance change under an open chat doesn't send it again.
• Invite Followed:
  • Link: App.kt's DeepLinkListener, which hears each link once. The cold-start path in MainRoot re-derives its routes on every auth re-emission and would count one link several times. The listener runs before auth resolves, so a logged-out tap on an invite counts as followed too.
  • QR: Scanner's GroupChatInvite branch.
  • Chat Card: an invite card in the transcript that opens a different group.

Tests

• GroupEventsTest and ChatEventsTest pin each new event's literal strings on the Android host, macosArm64 and iosSimulatorArm64. AnalyticsEventsTests.swift covers one group event through SharedCoreKit.
• ConversionsTest covers chatResult and gateMint.
• ChatGroupAnalyticsTest covers Gate Shown once, and without a mint for an ungated group. It also covers join and leave results, the invite, funding and info taps, and the chat card. There are also emission tests for create, edit and mute, using RecordingAnalytics.