[Bug]: Client not syncing when empty TAGS file is in folder

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

I'm syncing emacs org files (plaintext) across machines. When the notes folder contains a **TAGS** file with no content, nextcloud refuses to sync any changes from client to the server any more. The other way round works.

I'm running the server inside a docker container. I couldn't find any useful logs on the files chaned neither server-side nor client-side.

I though I share this since this issue caused my a few hours to figure out.

Pls let me know if I can somehow assist with the investigation.

### Steps to reproduce

Create some files in a empty directory. They should appear in the nextcloud WebUI.

Add a empty file called **TAGS** in the same directory. Changes to already existing files are not going to be synced any more. The client is convinced it's done syncing though.

Interestingly, when making a copy of the folder, only the subfolders (w/o content) are synced, no matter what's the content.

### Expected behavior

All files are synced.

### Which files are affected by this bug

*.*

### Operating system

Linux

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

Ubuntu 22.04.2 LTS @ 5.19.0-38-generic stock kernel

### Package

Distro package manager

### Nextcloud Server version

image: nextcloud:25.0

### Nextcloud Desktop Client version

3.4.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 Enabled

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

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

### Nextcloud Server logs

_No response_

### Additional info

_No response_

No source file, test, or entry point is identified in the issue. First reproduce the sync failure with an empty TAGS file in a folder using the Nextcloud Desktop Client, then inspect client and server logs while comparing behavior before and after adding TAGS. Done means existing and new file changes sync successfully to the server.

Written by the indexing model from the issue text.