fix: Force mute handling

[SystemKeeper]

Easier to check the commits individually.

• Fix1: Currently we only save the mute state when a forceReconnect is happening, so initiated by the app. What we fail to do is to save that state in other places e.g. reconnect from server, force mute by a moderator, etc. So you might end up unmuted again in the call
• Fix2: When a moderator force mutes the user which in that second tries to mute as well, the user might end up unmuted again, as the force mute overlapped the mute. We now add a cooldown phase so a user can only unmute again after a few seconds, when it was force-muted.
• Fix3: Keep the CallKit state in sync to properly indicate mute/unmute.
• Fix4: Also remember the video state across all reconnect paths.

🤖 AI (if applicable)

• The content of this PR was partly or fully generated using AI