jottacloud: fix incorrect modtime after setting a file's modtime

SetModTime kept the caller's full precision modtime in memory while
the server stores second precision, so until the object was re-read
the modtime did not match what a fresh listing would report. This
broke wrappers which compare exact modtimes, such as the hasher
backend's fingerprint and the VFS cache. Truncate the modtime to
second precision to match what the server stores.

backend/jottacloud/jottacloud.go

@@ -1876,8 +1876,10 @@ func (o *Object) SetModTime(ctx context.Context, modTime time.Time) error {
 		return err
 	}
 
-	// update local metadata
-	o.modTime = modTime
+	// update local metadata - the server stores modtimes with second
+	// precision so truncate here too to keep the in-memory modtime
+	// identical to the one a fresh listing returns
+	o.modTime = modTime.Truncate(time.Second)
 	return nil
 }