File uploads timeout too rapidly and can't be retried

[ara4n]

Steps to reproduce

1. Simulate bad network connectivity
2. Try to upload a file
3. Get frustrated

Outcome

What did you expect?

I expect the file upload to keep trying to upload until i have good connectivity - or at least queue up with a retry button like my other messages do.

What happened instead?

Instead, it gives up after ~30s and then deletes itself from the timeline, meaning i have no retry button, and i have to manually retry to upload again (plus it will now be out of order with my other queued messages). Worse still, you can't tell if the original send even worked, so you end up sending a duplicate (at least in an E2EE room). We're failing our own What Goes Wrong interview question :((

I'm pretty sure this is a regression and that we used to queue these correctly.

Operating system

macOS

Application version

Nightly

How did you install the app?

Nightly

Homeserver

matrix.org

Will you send logs?

No

[t3chguy]

We never had functionality to queue yet-to-be-uploaded messages, that's #9234