feat: ingest iOS push notifications via FCM Kafka topics

[code-lucasgabriel]

Add ingestion for the new push-_ios-(single|massive) topics so the GCM pusher can consume iOS messages alongside the existing Android ones.

• Extend topic regex in config and common.go to match the ios platform
• Add Platform field to KafkaMessage and populate it from the topic
• Subscribe pusher gcm to ios single/massive topics for every gcm app
• Cover new parsing and consumer behavior with unit tests

---

Note

Medium Risk
Adds a new field to the KafkaMessage struct and changes topic subscription/parsing, which can break downstream consumers or alter which Kafka topics are consumed if assumptions were implicit.

Overview
Enables ingestion of new push-<game>_ios-(single|massive) Kafka topics alongside existing gcm/apns topics by expanding the configured topic regexes and the GetGameAndPlatformFromTopic parser to recognize ios.

Propagates the parsed platform through the queue pipeline by adding Platform to interfaces.KafkaMessage, populating it in KafkaConsumer.receiveMessage, and updating GCMPusher to subscribe to both gcm and ios topics per app. Adds unit tests covering topic parsing and the new Game/Platform fields on consumed messages.

^{Reviewed by Cursor Bugbot for commit d78859e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d78859e. Configure here.}

[cursor]

iOS messages misreported as "gcm" in stats and operations

High Severity

The new Platform field on KafkaMessage is correctly populated (e.g., "ios" for iOS topics) but is never read by the firebase messageHandler. That handler hardcodes "gcm" in all ~10 call sites for stats reporting, feedback, dedup, and rate limiting. iOS notifications ingested via the new topics will be mislabeled as "gcm" everywhere — breaking per-platform metrics, sharing dedup keys and rate-limit buckets across platforms.

Additional Locations (1)

• interfaces/queue.go#L32-L33

 

^{Reviewed by Cursor Bugbot for commit d78859e. Configure here.}

[code-lucasgabriel]

It is part of the incremental development of the feature. Carry the platform value end-to-end through the Firebase message handler so that dedup, rate limiting, stats reporters, and feedback reporters use the actual platform (gcm or ios) instead of the hardcoded "gcm" string, is the next task in the development.