Desktop app can not use keys in keyring after it is unlocked

### Description
I am using KeePassXC, which uses libsecret, as my keyring where Element-desktop stores the necessary keys for decryption. KeePassXC locks itself each time the laptop is closed which means that Element cannot read any messages after opening the laptop while I did not unlock the password manager yet.
My problem is that Element can not decrypt the messages even if unlock the keyring.
It seems like Element does not check for an unlock, not even periodically.
This means that every time I close and open the laptop again I have to close the Element app, unlock the keyring and open Element back again.
(When not unlocking the keyring before opening Element, Element requests an unlock of the keyring but does not wait for it to succeed, failing again to decrypt the messages, but that probably will be a different github issue)

### Steps to reproduce

- Use a keyring that uses libsecret such as KeePassXC
- Unlock keyring (KeePassXC in this case)
- Open Element (*everything still works*)
- Lock keyring
- Wait for about an hour (Maybe some temporary key times out) -> Element cannot decrypt messages
- Unlock keyring
---
UPDATE (easier reproduction):
- Login into Linux user account
- Open Element
- Shows no connectivity as keychain is still locked
- Unlock keyring
---

At this point I expect Element to fetch the missing keys from the keyring and be able to decrypt the messages at some point of time, but it does not.

#### Screenshot of failed decryption

### Version information

- **Platform**: desktop
- **OS**: Arch Linux
- **Version**: 1.7.29

There is a relation to vector-im/element-desktop#874