[Bug]: renomming file with long path

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

When renaming a file (subfolder length is significant), we are limited by the number of characters to put. If we put the file locally on the computer, rename it, and put it back in the desired folder, it goes well, we can synchronize the file and we can read it. Why this renaming limitation if everything works?

### Steps to reproduce

1. Rename a file (long enough path)
2. We are limited by the number of characters to put

### Expected behavior

we can put the name we want

### Which files are affected by this bug

Windows explorer

### Operating system

Windows

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

Windows 11

### Package

Official Windows MSI

### Nextcloud Server version

29.0.8

### Nextcloud Desktop Client version

3.12.8

### 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?

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

### Nextcloud Server logs

_No response_

### Additional info

_No response_