Draft: handle invalid remote timestamp
Description
For an unknown reason, some synced files on the cloud got invalid timestamp remotly. In murena cloud database, the modified timestamp, creation timestamp and upload timestamp is set to max of unsigned int 32 (4294967295). Because of this, the infra team has no option to restore the correct timestamp value.
The only solution, is to force re upload of those file to send the expected timestamp.
Technical details
I use this opportunities to rewrite commonUtils/FileDiffUtils.java in kotlin and to move it into contentScanner package where it should be. The new file is: contentScanner/FileDiffChecker.kt
Tests
specific unit test for the new behaviour has not been written yet.