[stable-34.0] fix(libsync): folder move or rename data loss. - #10218

WebDAV lock tokens are bound to the URL they were issued for. When a
parent directory is renamed, PropagateLocalRename and
PropagateRemoteMove both copy child journal records to the new path
while preserving the old token. Subsequent uploads send the stale
token and receive 412/423 from the server.

Clear the token from the journal on either status code so the next
sync retries without it. Schedule rediscovery on 412 since the server
state is uncertain.

Force remote rediscovery on both 412 and 423 upload errors so the lock
state cleared from the journal is refreshed from the server, not only the
bad etag on 412. Strengthen the 412 test to assert the parent folder etag
is invalidated.

Add a matching Q_OS_WIN guard in testLockedStateClearedOnClientInitiatedRename
to clear the ACL before the local directory rename, which Windows requires
when files inside have an ACL-based read-only restriction.

Assisted-by: Claude Sonnet 4.6 <[email protected]>
Signed-off-by: Camila Ayres <[email protected]>

When a remote directory move is finalized, iterate all children
recorded in the sync journal and rewrite their paths to reflect the
new location, clearing stale lock state. Without this, children
retained the old path in the database and could be treated as new
uploads or silently lost on the next sync cycle.

Assisted-by: Claude Sonnet 4.6 <[email protected]>
Signed-off-by: Camila Ayres <[email protected]>

Signed-off-by: Camila Ayres <[email protected]>

Signed-off-by: Camila Ayres <[email protected]>

Signed-off-by: Camila Ayres <[email protected]>

Signed-off-by: Camila Ayres <[email protected]>

we might delete local client DB records when tracking server rename
leading to loose of state by the client that will trigger wrong sync
decisions

Signed-off-by: Matthieu Gallien <[email protected]>