fix(file-provider): Fix flaky testEnumerate root date assertion

MockRemoteInterfaceTests.testEnumerate compared the enumerated root file's date against the item's creationDate, but toNKFile() maps modificationDate onto NKFile.date. MockRemoteItem defaults creationDate and modificationDate to two separate Date() calls that are only sometimes identical, so the assertion flaked on CI when the clock ticked between them. Compare against modificationDate, the field the value is actually derived from.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Iva Horn <iva.horn@nextcloud.com>

Author: 2 people

shell_integration/MacOSX/NextcloudFileProviderKit/Tests/InterfaceTests/MockRemoteInterfaceTests.swift

@@ -503,7 +503,12 @@ final class MockRemoteInterfaceTests: XCTestCase {
         XCTAssertEqual(targetRootFile?.ocId, expectedRoot?.identifier)
         XCTAssertEqual(targetRootFile?.fileName, NextcloudKit.shared.nkCommonInstance.rootFileName) // NextcloudKit gives the root dir this name
         XCTAssertEqual(targetRootFile?.serverUrl, "https://mock.nc.com/remote.php/dav/files/testUserId") // NextcloudKit gives the root dir this url
-        XCTAssertEqual(targetRootFile?.date, expectedRoot?.creationDate)
+        // `toNKFile()` maps the item's `modificationDate` onto `NKFile.date`, so compare against
+        // that — not `creationDate`. `MockRemoteItem.init` defaults `creationDate` and
+        // `modificationDate` to two separate `Date()` calls, which are usually (but not always)
+        // identical; comparing `date` to `creationDate` therefore passed only when the clock did
+        // not tick between those two calls, and flaked on CI when it did.
+        XCTAssertEqual(targetRootFile?.date, expectedRoot?.modificationDate)
         XCTAssertEqual(targetRootFile?.etag, expectedRoot?.versionIdentifier)
 
         let resultChildren = await remoteInterface.enumerate(