draft: feat(fileprovider): Handle Affinity lock files

[claucambra]

Resolves

#10392

Summary

Handle automatic file locking for Affinity lock files in FileProvider sync engine

Checklist

• Sign-off message is added to all commits.
• The commit history is clean with no merge commits.
  • How to rebase your commits
  • How to squash commits with rebase
• Uploaded screenshots from before and after for UI changes.
• Test(s) added to branch, with before/after results included in PR description, for performance improvements where applicable.
• Documentation has been updated or is not required.
• [] Backports requested where applicable (critical bugfixes).
• Labels added where applicable (bug/enhancement).
• Milestone added for target version.

AI (if applicable)

• The content of this PR was partly or fully generated using AI
  • I have read the guidelines for AI-assisted contributions.
  • I have read Nextcloud's AI Contribution Policy.

[i2h3]

Not now but at some point we should consider refactoring the whole lock detection and management into something more scalable.

[i2h3]

/backport to stable-34.0

[github-actions]

Artifact containing the AppImage: nextcloud-appimage-pr-10409.zip

Digest: sha256:e33ae954533bfb97ccd487c1b56f7fd2edc2e4c352abbe50658ce8881767c027

To test this change/fix you can download the above artifact file, unzip it, and run it.

Please make sure to quit your existing Nextcloud app and backup your data.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[claucambra]

this is not working as expected. The lock files are not being detected/handled by the File Provider extension...