Fix volume loop on casting

[albertonantiattheo]

UIContainer.muted setter unconditionally writes back to player.muted on every volumechange event, creating a feedback loop when the cast receiver cannot converge on the sender's expected volume state.
This PR prevents a feedback loop during casting by guarding against redundant writes.

[changeset-bot]

🦋 Changeset detected

Latest commit: 722923a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@theoplayer/web-ui	Patch
@theoplayer/react-ui	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[MattiasBuelens]

Huh, I would have thought the Web SDK already handled redundant writes on it own... 🤔 Could you raise this issue internally too?

Also, please add a changelog entry. See the bot's comment (above) for instructions. 😉

[albertonantiattheo]

Changelog added. The topic is also tracked internally in a ticket.
Re why the player doesn't check it, I think it may be because it never came up...: the VJS UI calls setMuted only on user clicks, not for every volumechange, so it doesn't start a loop (IF I am reading this correctly, of course).

[MattiasBuelens]

Thanks! For consistency, I've also added checks in similar places where we update the player's properties. 😉