Prevent tracking channel states for malformed CIDs

[gpunto]

Goal

Prevent the SDK from tracking ChannelStates by a malformed cid. The original symptom is in SyncManager.updateActiveChannels: it issues a Filters.in("cid", missingCids) query on reconnect, and a single malformed entry in the list fails the whole request, blocking re-watch for every valid channel in the same batch. The underlying problem is that StateRegistry/LogicRegistry happily store state keyed by an unvalidated (channelType, channelId) pair, so malformed cids can leak in through any code path that bypasses the existing validateCidWithResult gates (sync recovery, channelFromMessage, etc.).

Closes AND-1187.

Implementation

• New internal ChannelId value class with fromCid / fromTypeAndId factories that return null on invalid input.
• StateRegistry and LogicRegistry re-key their channel maps on ChannelId. Their public channel(type, id) entry points validate at the boundary; malformed input returns a fresh, non-cached state/logic.
• StateRegistry.getActiveChannelStates() now returns Map<ChannelId, ChannelState>, so SyncManager.updateActiveChannels and EventHandlerSequential iterate validated keys directly.
• QueryChannelsStateLogic.addChannelsState filters out malformed server channels upfront so they never reach setCids / setChannels / logicRegistry.

Testing

• New ChannelIdTest covers fromCid / fromTypeAndId.
• StateRegistryTest and LogicRegistryTest: malformed cid returns a non-cached state/logic and the registry maps stay empty.
• QueryChannelsStateLogicTest: getActiveChannelState returns null on malformed cid; addChannelsState drops malformed channels from setCids / setChannels / logicRegistry.

[github-actions]

PR checklist ✅

All required conditions are satisfied:

• Title length is OK (or ignored by label).
• At least one pr: label exists.
• Sections ### Goal, ### Implementation, and ### Testing are filled, or the PR is bot-authored.
• An issue is linked (Linear ticket or GitHub issue), or the PR is bot-authored.

🎉 Great job! This PR is ready for review.

[github-actions]

SDK Size Comparison 📏

SDK	Before	After	Difference	Status
stream-chat-android-client	5.88 MB	5.88 MB	0.00 MB	🟢
stream-chat-android-ui-components	11.11 MB	11.11 MB	0.00 MB	🟢
stream-chat-android-compose	12.53 MB	12.53 MB	0.00 MB	🟢

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
85.4% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud