Set QuickXorHash as checksum to compare file changes

[dkocher]

Extract UUID from ETag formatted as "{D7751A14-FEA5-4BDA-969E-F8022E58B7E7},9" which remains constant when moving files.

[AliveDevil]

We have Hashes for Files available already:
https://github.com/iterate-ch/onedrive-java-client/blob/develop/src/main/java/org/nuxeo/onedrive/client/types/File.java#L9-L11

quickXorHash is guaranteed to be available.

[AliveDevil]

Alternatively, use the cTag¹-property:

An eTag for the content of the item. This eTag isn't changed if only the metadata is changed. Note This property isn't returned if the item is a folder. Read-only.

Relying on a implementation detail of the eTag is dangerous.

Footnotes

1. https://learn.microsoft.com/en-us/graph/api/resources/driveitem?view=graph-rest-1.0#properties ↩

[Copilot]

Pull Request Overview

This PR implements UUID-based checksum comparison for OneDrive/SharePoint by extracting UUIDs from ETag values that remain constant when moving files, enhancing file synchronization accuracy.

• Modifies Checksum class to support UUID extraction from ETag values formatted as "{UUID},version"
• Updates OneDrive features to use checksum-based comparison instead of timestamp-only comparison
• Adds comprehensive test coverage for checksum behavior during file operations

Reviewed Changes

Copilot reviewed 21 out of 21 changed files in this pull request and generated 2 comments.

File	Description
core/src/main/java/ch/cyberduck/core/io/Checksum.java	Enhanced checksum parsing to support Base64 and improved hex string handling with proper validation
onedrive/src/main/java/ch/cyberduck/core/onedrive/features/GraphAttributesFinderFeature.java	Added checksum extraction from OneDrive file hashes (QuickXorHash)
onedrive/src/main/java/ch/cyberduck/core/onedrive/GraphProtocol.java	Updated comparison service to use checksum-based comparison with fallback to timestamp
onedrive/src/test/java/ch/cyberduck/core/onedrive/*Test.java	Added comprehensive test assertions for checksum behavior during write and move operations

[AliveDevil]

This relies on quickXorHash always being 20 Bytes, and is misrepresented as SHA1.

[dkocher]

You are right. Full implementation requires us to implement quickXorHash as a ChecksumCompute feature.