Overview of fixes for possible data loss

### To be released in 4.0.11, 33.0.6 and 34.0.0:
#### File provider
- [x] #10130
Fixes a bug where renaming or deleting a folder could accidentally affect a sibling folder that starts with the same name (e.g. deleting photos would also touch photos-backup).
- [x] #10134
Fixes a reported bug: a file opened in an editor could not be saved after its parent folder was renamed on another device. The save was silently rejected by the server.
=> https://github.com/nextcloud/desktop/issues/10173
=> https://github.com/nextcloud/desktop/issues/10163

- [x] #10135
Prevents files from disappearing when a folder is moved or renamed on another device. Also protects files that are mid-upload from being deleted.

~~TBD: #10136 - When LibreOffice (or similar cross-platform editors) saves a file after its parent folder was renamed, it recreates the old folder on the server producing a duplicate. This PR blocks that duplicate from being created.~~

#### Standard sync
~~- TBD https://github.com/nextcloud/desktop/pull/10001
Correctly follows folders through multiple successive server side renames even when they contain files that were never uploaded.~~
- [x] https://github.com/nextcloud/desktop/pull/9998
Similar to #10134 and #10135. When a parent folder is renamed during sync, file changes inside it can be silently lost.