Not able to sync after changing global Ignore List

### ⚠️ 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 have searched for 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

After adding `.venv` to the global ignore list i got an `The Server responded with an error while reading Folder xyz` Error on almost all Folder synchronizations.

Than i removed `.venv` from the list an the error is still there.

I am using the latest Debian build since a few years on multiple devices an never used this feature, now two devices are nearly unable to sync (i have done this one two machines).

The problem is that i sync about 2TB over a rather slow Internet connection so in can't play around or re sync everything.

### Steps to reproduce

1. Add `.venv` to ignore list
2. change a file
3. wait for sync

### Expected behavior

syncing the file like usual.

### Which files are affected by this bug

any file or folder

### Operating system

Linux

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

Debian 13

### Installation method

Community PPA (please test with the AppImage package ?)

### Nextcloud Server version

32.0.9

### Nextcloud Desktop Client version

3.16.7daily (Debian)

### Did this occur after an update or on a clean installation?

Clean desktop client installation

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

No

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

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

### Nextcloud Server logs

```shell

```

### Additional info

_Could not provide client/server log because they are way to big for GitHub_