[Bug]: 3.14.1 We received a different E-Tag for resuming

### ⚠️ 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

On Windows 10 64-bit clients, "Settings", the following message keeps appearing:
`We received a different E-Tag for resuming`
The log file for the corresponding folder sync contains:
```
#=#=#=# Syncrun started 2024-10-23T10:39:30Z
#=#=#=#=# Propagation starts 2024-10-23T10:39:30Z (last step: 661 msec, total: 661 msec)
||Profiles/rdvpq1tu.unconfigured/addons.json|64|2|1729630493|e456f7673c31b06136ba89178d6d6716|2325|17711359oc3hd6f2u8cw|2|We received a different E-Tag for resuming. Retrying next time.|200|2325|1729198478|f012bd95-2f10-4760-bed8-8f2677c2db60|
#=#=#=# Syncrun finished 2024-10-23T10:39:31Z (last step: 322 msec, total: 984 msec)
```
This started to appear after server upgrade to 30.0.1.

### Steps to reproduce

1. Run nextcloud client as normal
2. Monitor using "Settings"
3. Observe red "(X)" (fail to sync icon) occurring repeatedly with `We received a different E-Tag for resuming`

### Expected behavior

No failures should occur or be visible in the settings dialogue.
Either this is a genuine bug: the E-Tag should never be different, there is some underlying problem;
Or this is expected behaviour, a retry should be automatically invoked, and the user should never be alerted to such.

### Which files are affected by this bug

Any/many files in different folders, eg addons.json

### Operating system

Windows

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

Windows 10

### Package

Official Linux AppImage

### Nextcloud Server version

30.0.1

### Nextcloud Desktop Client version

3.14.1

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

Updated from a minor version (ex. 3.4.2 to 3.4.4)

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

Encryption is Disabled

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

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

### Nextcloud Server logs

No warnings or errors reported on server.

### Additional info
```
Installed Packages
httpd.x86_64 2.4.62-2.fc40 @updates
mariadb.x86_64 3:10.11.9-1.fc40 @updates
php-fpm.x86_64 8.3.12-1.fc40 @updates
redis.x86_64 7.2.6-1.fc40 @updates
```

Start by reproducing the repeated sync failure on Windows 10 with Nextcloud Desktop Client 3.14.1 and Server 30.0.1, then inspect the sync log entry for addons.json. Done means determining whether the E-Tag mismatch is a real synchronization problem or an expected retry that should not appear as a visible failure.

Written by the indexing model from the issue text.