[mogita]

Problem

ChannelTest > Can mute a channel fails on most CI runs. It mutes a channel and reads the member back at once, and the read can come from an API node that still holds the user from before the mute.

Solution

The two member reads poll with the existing waitFor helper until notifications_muted is true. The same change went into stream-chat-net for the same reason.

How to verify

1. The CI run on this PR passes, including Can mute a channel.

---

Note

Low Risk
Test-only change; no production or API behavior is modified.

Overview
Stabilizes Can mute a channel by polling member reads after a mute instead of asserting immediately. Both checks—plain Channel.queryMembers() and the same query with filterCondition("notifications_muted", true)—now run inside the existing waitFor helper until the test user’s member reports notifications_muted as true, with a comment noting short-lived API node caching for offline users.

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