Element shows ping when a message with `@room` is deleted

### Steps to reproduce

1. Be in a room where notifications settings are set to **All messages**.
2. Another user sends a message in that room. (Will trigger notification.)
3. That same other user deletes their message. (Will trigger another notification.)

### Outcome

#### What did you expect?

I should get notified for the message with `@room`. However, I should not receive any notification for the deletion of that message.

#### What happened instead?

I got pinged twice. Once when the message is sent, and again when the message is removed. The second ping only appears in Element, it doesn't send the notification through to my OS.

### Operating system

Debian 13 (Trixie)

### Application version

Element version: 1.11.110 Crypto version: Rust SDK 0.13.0 (f64839e), Vodozemac 0.9.0

### How did you install the app?

https://element.io/download#linux

### Homeserver

one.ems.host

### Will you send logs?

Yes

### Context

I've written a Matrix bot that just pings everyone in the room and announces when one of us goes live on Twitch. It then deletes the message when the streamer goes offline.

For Element users, I've found this is actually causing users to get pinged when the streamer goes offline, which doesn't seem intended. There wouldn't be much benefit to ping a user about a deleted message.

Start by reproducing the notification-settings and message-deletion sequence described in the issue, using a room set to All messages and a message containing @room. Trace the Element notification handling for the deletion event. Done means the original @room message still notifies the user, while deleting it produces no second in-app ping or OS notification.

Written by the indexing model from the issue text.