bug: starting an encrypted direct conversation from mobile fails to find key

Describe the Bug

There is a race condition when starting a direct message from mobile to a recipient on the server website. The recipient will often create the room key and create a E2ESuggestedKey in the sender's subscription. But the sender will not evaluate it because it does not listen to subscription changes yet (it lost the race).

Steps to Reproduce

1. Log in with the recipient user to the server website.
2. Make sure there is no direct message room existing between the sender and recipient.
3. Use the sender's mobile device to start a direct message to the recipient.
4. You will 90% of the time see that you should wait a while to get the E2E key and that will never happen if nothing else is done.

Expected Behavior

Starting a direct message with someone should allow sending a message immediately, without waiting for keys.

Actual Behavior

Starting a direct message for the first time with a recipient which is logged on to the server website will result in a "wait for keys" message that will not go away on its own.

Rocket.Chat Server Version

7.9.3

Rocket.Chat App Version

4.63

Device Name

iPhone 16 Pro, Android Pixel 7

OS Version

iOS 16, Android API 35

Additional Context

No response