Element causes KISS launcher to refresh UI needlessly.

### Steps to reproduce

1. Element is installed and is active in background, connected to a private Conduit server.
2. No Matrix-related activity is happening (i.e. no incoming messages, calls, etc.)
3. The device is idling, screen is on. For example, "KISS launcher"'s context menu is open for some app.

### Outcome

#### What did you expect?

No disruptions / broadcasts are coming from Element, as no Matrix-related activity is happening.

#### What happened instead?

Sometimes KISS Launcher spontaneously refreshes all apps' icons, also closes context menu (a bug in KISS Launcher probably).

`adb logcat` shows `CompanionDeviceManagerService: onPackageModified(packageName = im.vector.app)` from system_server when this happens.
`im.vector.app` itself only produces boring `OrientationModule: onActivity*` adb messages.

---

This does not happen in Element is stopped, e.g. using "Hibernate" action of KISS launcher or (maybe?) disabling notifications for the Element session in Element settings.

Apart from periodic, every minute trigger, same event is also triggered when I re-launch Element after pressing "back" button (but not just when navigating away from the view by go-to-home or switch-apps gestures).

The periodic trigger seemed to disappear as I experimented with the problem while composing this issue, though I see many prior logcat messages from today and yesterday, typically with a 1 minute and 7 seconds periodicity.

Triggering "Troubleshoot Notifications" and observing the demo notification does not trigger onPackageModified.

In system notifications settings, Element's notifications are enabled, except of the "Listening for events" one.

### Your phone model

Google Pixel 3 XL

### Operating system version

Android 12 + Magisk

### Application version and app store

1.5.32 from F-Droid.

### Homeserver

Conduit 0.4.0

### Will you send logs?

No

### Are you willing to provide a PR?

No