[Bug]: Sync Conflicts in change case (regular <> CAPS)

### ⚠️ This issue respects the following points: ⚠️

- [x] This is a **bug**, not a question or a configuration/webserver/proxy issue.
- [x] This issue is **not** already reported on [Github](https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3Abug) OR [Nextcloud Community Forum](https://help.nextcloud.com/) _(I've searched it)_.
- [x] Nextcloud Server **is** up to date. See [Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) for supported versions.
- [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/).

### Bug description

Changing the case of a file and adding some text and adding a file with the same name, but with a Case difference results in mayhem!

### Steps to reproduce

1. install the Desktop Client on a Windows machine
2. have a file called "image of old church.jpg"
3. have a successful sync
4. rename it to "image of OLD church1.jpg" (via web interface)
5. add file "image of OLD church.jpg" (via web interface; different file, different size, different image/content)
6. try and sync....

And you get an error with a "conflict in case" (translated form Dutch)
The conflict is created with the file named at point 2 with the file named at point 4

### Expected behavior

I expected the files to sync.. that the NextCloud sync would see the rename and..

### Nextcloud Server version

30

### Operating system

RHEL/CentOS

### PHP engine version

PHP 8.1

### Web server

Apache (supported)

### Database engine version

MariaDB

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

None

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

Encryption is Disabled

### What user-backends are you using?

- [x] Default user-backend _(database)_
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other

### Configuration report

```json
-
```

### List of activated Apps

```shell
-
```

### Nextcloud Signing status

```shell
-
```

### Nextcloud Logs

```json
-
```

### Additional info

I have an automated system and there (apparently) was a case change at the source. the "1" is added to keep different files with the same name. So the order and the case changed.. Now I have thousands of these conflicts..

I fear the only way is to remove the share, delete the local files and re-sync the many thousands of files.. But that is the most ugly way of doing it.. (every time there is a sync?!)