Overview of fixes for possible data loss

[camilasan]

To be released in 4.0.11, 33.0.6 and 34.0.0:

File provider

• fix(file-provider): use slash prefix for child item queries. #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).

• fix(file-provider): prevent data loss when parent folder moves during sync. #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.
  => Defer parent folder deletion or re-parent file after upload #10173
  => Coordinated Renames in File Provider #10163

• fix(file-provider): invalidate lock tokens when file paths change.  #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 #10001
Correctly follows folders through multiple successive server side renames even when they contain files that were never uploaded.

• fix(libsync): folder move or rename data loss. #9998
  Similar to fix(file-provider): prevent data loss when parent folder moves during sync. #10134 and fix(file-provider): invalidate lock tokens when file paths change.  #10135. When a parent folder is renamed during sync, file changes inside it can be silently lost.

[tomdereub]

I think this one should be considered too : #9858
It's made a big mess in my company last week, just testing 33.0.5 on one computer...