Sync exclusion patterns ignored, causing slow uploads and "could not create path" errors

The `.sync-exclude.lst` file is not effectively preventing file synchronization for specified patterns, leading to significant synchronization issues.

## Current Behavior
- Specified exclude patterns in `.sync-exclude.lst` are not being properly honored
- Files/directories that should be excluded continue to be processed
- Synchronization attempts for excluded files result in:
- Extremely slow upload process
- "Could not create path" error messages (wherever that come from)
- Unnecessary network and system resource consumption

## Expected Behavior
- `.sync-exclude.lst` should completely prevent synchronization of specified file/directory patterns on client-side
- Excluded files and directories should be skipped during the sync process
- No error messages or attempts to sync excluded content

## Steps to Reproduce
1. Attempt to exclude patterns via Nextcloud Client UI
2. Create a `.sync-exclude.lst` file in the sync directory
3. Add the same exclude patterns (e.g., `CaptureOne/Cache/*`) in both locations
4. Attempt to synchronize the directory
5. Observe that excluded files/directories are still being processed despite using multiple exclusion methods

## Exclusion Methods Attempted
- Excluded via Nextcloud Client's built-in ignore files
- Created `.sync-exclude.lst` with identical exclude patterns
- Both methods failed to prevent synchronization of specified files/directories

## Example Exclude Patterns Not Working
```
CaptureOne/Cache/*
CaptureOne/Cache/Proxies/*
CaptureOne/Cache/Thumbnails/*
```

## Environment
- Nextcloud Client Version: 3.16.2
- Operating System: macOS 15.3.2
- Nextcloud Server Version: Nextcloud Hub 10 (31.0.2)

The current behavior significantly impacts the usability of the Nextcloud client, especially for users with large directories containing cache or temporary files.