test/scenarios/remote: Don't flush local events
test/scenarios/remote: Don't flush local events

  Remote scenarios are played in 2 steps:
  - fetch and apply remote changes
  - process and apply resulting local changes

  To make sure we wouldn't miss local events during the second step,
  we would wait for a smal delay and then manually flush them.
  However, we could end up flushing them too early so we'll now wait
  for the `local-end` sync status to be emitted by the local watcher
  at the end of the events processing. This is only possible now that
  we emit this status with a delay after the latest processed event in
  the Atom watcher (i.e. since we're processing events as a stream, we
  don't really know when an event in the last one so we wait before
  emitting the status. If another event comes in, we reschedule the
  status change).

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