Model inconsistency in case of nested synchronization roots

Steps to reproduce:

• Create a workspace named Workspace and a folder under it: Workspace / Folder and a file name File.txt under it
• Mark Folder as sync root
• Wait for the client to pick it up
• Mark the Workspace as sync root

Observed: both Folder and Workspace are available as sync roots in the local file system and File.txt is synchronized twice. This is problematic because because when adapting a document (e.g. File) after a change event in the audit log, one walks up the hierarch building the parent path to send the adapted FS item to the client to take the change into account. In our case only the File under Folder will be adapted as we make the simplifying assumption that a document can be mapped into a single node in the virtual FS tree (only one path).

To fix this model inconsistency we should unbind any existing sub nest roots when binding a container up in the physical repository document tree.