allow linux desktop app to work asynchronously

[r2evans]

The issue template didn't fill for this (some hints that it's a GH problem), so some standard stuff:

• This is a bug, not a question
• This issue is not previously reported
• server/client are up to date
• I agree to the https://nextcloud.com/contribute/code-of-conduct/

Bug Description

The desktop hangs for various reasons. This happens frequently but not all of the time, and the logs suggest it is busy downloading the list of files (usually not file contents themselves, I have VFS enabled). If I try to open "settings", it can take between 10-60 seconds for the UI to appear, and even then it often hangs (and gnome issues the "hung" dialog, offering to "Force Quit" or "Wait"). Eventually it catches up and all works well again until it tries to connect again.

One of my (two) configured NC profiles has over 50K files (the other over 10K), not sure if that is "a lot" by NC standards. Bandwidth limits are not set, and there are no bandwidth "problems": one of my NC servers is on the same network, and both my internet and the other server are on 200+ Mbps.

I'm confident that most of the desktop application for linux is written in an asynchronous manner, there is at least one code block having to do with network traffic that is not asynchronous.

The app works, but doing anything to it (pause, open settings, open about) will not work immediately if/when the client is syncing files or even just a file list.

Steps to reproduce

1. Configure a profile that has many files, regardless of file-size.
2. Enable VFS on linux.
3. Attempt to bring up and interact with the client window while it is syncing

Server OS: ubuntu-22.04, fresh install (in docker)
Client OS: ubuntu-24.04, gnome-46
Client app version: 3.14.2-20241021.144050.4eec4f3d3-1.0~noble1

Encryption? no

External user-backend? saml on the remote server, default on the local

Server logs have no errors or warnings.

Client logs: I will add some when I can get it to re-trigger and isolate which of the logfiles is the culprit (otherwise I'd be uploading tons of logs without knowing which indicates the problem, not helpful to you).