[Bug]: Warnings on files that could not by synced (MacOS Nextcloud App)

### ⚠️ Before submitting, please verify the following: ⚠️

- [x] This is a **bug**, not a question or a configuration issue.
- [x] This issue is **not** already reported on Github (I've searched it).
- [x] Nextcloud Server and Desktop Client are **up to date**. See [Server Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) and [Desktop Releases](https://nextcloud.com/install/#install-clients) for supported versions.
- [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/)

### Bug description

Very often I get cryptic warnings about files not being synced:

"Some files could not be synced. See below for warnings"
and what follows "below" is an endless list of changes without any errors or warnings.

There is no way to filter the list, nor to diagnose the problem from the list of files.

### Steps to reproduce

1. Notice warning symbol on the Nextcloud app tray icon
2. Click on the top bar symbol of Nextcloud (Stable Channel)
3. Get perplexed...

### Expected behavior

I want to see the failed sync attempts with description and have a way to filter the list of files to see errors.
If files failed to sync, it is obviously relevant to be on top of the list and have some description about the failure and which files were affected.

Warnings and failures to sync files should simply be visible clearly in the app and not hidden behind multiple layers of menus, settings, exported nested archive files that I need to redact.

### Which files are affected by this bug

That's the bug! I whish I knew.

### Operating system

macOS

### Which version of the operating system you are running.

14.8.2

### Package

Official macOS Virtual files 12+ universal pkg

### Nextcloud Server version

same in beta (32) and stable

### Nextcloud Desktop Client version

4.0.2

### Is this bug present after an update or on a fresh install?

Fresh desktop client install

### Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

### Are you using an external user-backend?

- [x] Default internal user-backend
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other

### Nextcloud Server logs

```shell

```

### Additional info

I mean seriously, are you expecting every bug reporter to unpack (nested!) archive log files to redact sensitive data before submitting? Is this a joke? Should the sensitive information not be omitted by default?