As a user, when I remove Read rights from a synchronized folder/workspace, I expect an action on the local folders

Handle permission updates server side, typically grant Read <=> creation, deny Read <=> deletion

Currently the permission updates server side are not detected by the audit change finder.
Thus several cases are not dealt with, for example:

• Denying Read access on a document should mark the file/folder as 'unsynchronized' in the local DB if it has been locally modified since last synchronized (to keep the local changes), else delete it. Currently the file/folder stays in the client hierarchy and the last known states table, therefore any operation on it will crash, typically in the case of a folder trying to create a child file.
• Granting Read access on a document should be considered by the client either as:
  • A creation if it doesn't exist locally.
  • A match with a file system item existing locally