Key request modal is misleading and panic-inducing

### Steps to reproduce

1: Receive a message for which you don't have the keys:

> ** Unable to decrypt: The sender's session has not sent us the keys for this message. ** Re-request encryption keys from your other sessions.

2: Tap on "Re-request encryption keys" text.

### Outcome

#### What did you expect?

I don't know what I expected, but it wasn't this.

#### What happened instead?

I was told:

> Request Sent
Your unverified session 'Element' is requesting encryption keys.

WTF? Not only do I not have any unverified sessions, but none of my sessions are called "Element". This message is misleading, and panic-inducing because it states that at least one session exists that I did not know about and that is not under my control.

### Your phone model

iPhone

### Operating system version

16.1 (20B82)

### Application version

1.9.9 (20221018161714)

### Homeserver

_No response_

### Will you send logs?

No

Reproduce the key request flow on an iPhone running the reported iOS and app versions: open a message that cannot be decrypted, then tap “Re-request encryption keys.” Inspect the modal that reports an unverified “Element” session. Done means the message accurately identifies the requesting session or explains the request without implying an unknown session exists.

Written by the indexing model from the issue text.