core/pouch: Fake remote change on Cozy Notes
core/pouch: Fake remote change on Cozy Notes

  We want to avoid creating dispensable conflicts on Cozy Note exports
  that were not successfully saved on the local filesystem.

  We're now creating conflicts when we detect a local change on a Cozy
  Note export file. If we couldn't propagate a remote note modification
  to the local filesystem, we'll necessarily have a difference between
  the local file checksum and the one saved in PouchDB while the record
  can still be marked as synchronized if we've reached the 3 errors
  limit.
  This leads to the detection of a local modification during an initial
  scan.

  We'll migrate all existing notes to update their `sides` so that the
  local side will be out-of-date. In this situation, the local
  "modification" will be dropped in favor of a new download of the
  remote version.
  Now that we don't have any write issues on local note export files,
  all notes will be synchronized and we'll avoid conflicts.

cozy-labs/cozy-desktop,cozy-labs/cozy-desktop,cozy-labs/cozy-desktop,cozy-labs/cozy-desktop