[Bug]: macOS behavior when file name is too long.

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

Nextcloud Desktop behaves strange when you accidentally create a file with a too long file name.

If you delete the file again, the client is still stuck with an exclamation mark, that it is unable to sync the file because of the long file name. You have to rename the file you already deleted to solve this issue. The GUI to rename the file is way too wide (width of the file name). It will then show as synced, but not actually have created the renamed file.

### Steps to reproduce

1. Create a file that has a very long file name

2. Move file into nextcloud folder

3. Nextcloud shows an error

4. Delete the file

5. Nextcloud still shows an error

6. Try to solve it by clicking the renaming button in the sync list

7. GUI popup that opens is way to wide

8. rename the file in the pop up

9. Nextcloud client now shows that A1 (or whatever name you gave it) is synced.

10. But A1 is nowhere to be found, not on the client, not online

11. Even other clients (that were offline during all of that), will now show that A1 was successfully synced.

### Expected behavior

Rename GUI should have a default width instead of of the width of the file name

When a too long file gets deleted, no longer show it as error in the client.

When you rename a file (that no longer exists, because you deleted it) don't show it afterwards as syncec.

### Which files are affected by this bug

n/a

### Operating system

macOS

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

macOS 26.1

### Package

Official macOS 12+ universal pkg

### Nextcloud Server version

32.0.1)

### Nextcloud Desktop Client version

4.0.1 (macOS)

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

Updated from a minor version (ex. 3.16.1 to 3.16.2)

### 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
- [ ] Other

### Nextcloud Server logs

```shell

```

### Additional info

_No response_