DMs defect, mute malfunction

### Steps to reproduce

1. Create any change that modifies the state of functions (e. g. mute/unmute a DM or read mentioned messages)
2. Experience that the user act does not change the state as it should (e. g. muted DM is left untouched or the previously reviewed mentioned messages remain as unread.

Sharing presence doesn't change read sensing behavior, so rooms stay as unread until sending messages, even though it has been read before.

When taking a look at the mute malfunction, logging out or clearing cache doesn't help.

### Outcome

#### What did you expect?
I expected to mirror the user actions with the application behavior, but it didn't.

#### What happened instead?
Described above.

**Note that the issue doesn't only happen on my phone it's rather universal.**

### Your phone model

OnePlus 8, Samsung A55, Pixel 9

### Operating system version

Android 13, Android 15, Android 15

### Application version and app store

Element X G-Play 25.04.0

### Homeserver

Matrix.org

### Will you send logs?

Yes*

### Are you willing to provide a PR?

No

_*both of the communicating parties have sent their logs to your endpoint for further investigation._

The issue names no source files, tests, or entry points. Reproduce the mute and unread-state behavior on the listed Android versions, then inspect the submitted logs while tracing DM and mention state changes; done means those user actions consistently update room state without requiring a new message.

Written by the indexing model from the issue text.