[Bug]: Renaming and moving file before sync locking client

[four-bytes-robby]

Nextcloud_sync.zip
nextcloud-server.zip

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

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

If you rename and move several files one by one you might be ahead of the sync of the nextcloud client.
This will cause problems up to locking the client completely and not finding its way back to synchronization.
Client process has to be ended and restarted.

Steps to reproduce

Hard to reproduce but if you move several files fast enough into a folder and back plus doing renaming it will happen.
If you accidently moved a file into a folder for example it should not be necessary to wait for synchronization before moving it to another folder.
This might be due to downloading files and uploading changes / moves at the same time.
This problem was present with all versions I have tried starting from 3.13.2

Expected behavior

Sync should notice changes but not block the client.

Which files are affected by this bug

• all kind of files -

Operating system

Windows

Which version of the operating system you are running.

Windows 11 Pro 22H 22621.4169

Package

Official Windows MSI

Nextcloud Server version

29.0.6

Nextcloud Desktop Client version

3.14.0

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

attached as file

Additional info

Uploaded anonymized logs.