[Bug]: Regression in 4.0.8 – Sync error "Error transferring ... server replied: Not Found" on MS Access lock files (.ldb)

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

The client fails to handle Microsoft Access lock files (.ldb) correctly, resulting in persistent "Error transferring ... server replied: Not Found" sync errors. This was working as expected in version 4.0.7, but the issue appeared immediately after updating to 4.0.8.

### Steps to reproduce

1. Update (or install) Nextcloud Desktop Client 4.0.8 on Windows 10.
2. Open any .mdb file within the sync folder using MS Access.
3. MS Access creates a temporary .ldb file.
4. .ldb file gets stuck in syncing state (blue arrows icon)

### Expected behavior

The client should sync .ldb files as ordinary files.

### Which files are affected by this bug

.ldb

### Operating system

Windows

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

Windows 10

### Package

Official Windows MSI

### Nextcloud Server version

32.0.6.1

### Nextcloud Desktop Client version

4.0.8

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

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

### Nextcloud Server logs

```shell

```

### Additional info

_No response_