Change SingleMerge to only use second precision when comparing last modified

Otherwise you get problems with one file system uses seconds and
another milliseconds and suddenly two files that are created at
the same time does not have the same timestamp.

Makes the test suite take 2 seconds longer to run but it is
what it is.

1 files changed, 0 insertions, 3 deletions

diff --git a/libs/io/src/test/java/org/the_jk/cleversync/io/SingleMergeLocalTest.kt b/libs/io/src/test/java/org/the_jk/cleversync/io/SingleMergeLocalTest.kt
index 07cc848..d13213c 100644
--- a/libs/io/src/test/java/org/the_jk/cleversync/io/SingleMergeLocalTest.kt
+++ b/libs/io/src/test/java/org/the_jk/cleversync/io/SingleMergeLocalTest.kt
@@ -3,7 +3,6 @@ package org.the_jk.cleversync.io
 import org.junit.Rule
 import org.junit.rules.TemporaryFolder
 import org.the_jk.cleversync.local.LocalTreeFactory
-import kotlin.time.Duration.Companion.milliseconds
 
 class SingleMergeLocalTest : BaseSingleMergeTest() {
     @Rule
@@ -21,6 +20,4 @@ class SingleMergeLocalTest : BaseSingleMergeTest() {
     }
 
     override fun targetSupportsSymlinks() = true
-
-    override fun minModificationTime() = 10.milliseconds
 }