In case of checksum conflict "synced" file will always
take precedence as the sync is one way so the "syncing" deployment
is the one from which the file originates and in case previous
attempt to sync was interrupted, it should be allowed to overwrite.
FIX storageSync checksum conflict behaviour …