* commit '683a5bc1':
  ZP-849 SYNC_STATUS_FOLDERHIERARCHYCHANGED is always global and should be transmitted like a common status code (fix for BB), AdditionalFolders API and statically shared folders work always with backendids (they are internally mapped and transmitted with integerIds), expose integerIds in the listing of the AdditionalFolders API as "syncfolderid", generate integerid when an additional folder is added, have ZPush::$addSyncFolders and DeviceManager()->GetAdditionalUserSyncFolders() always work on backendIds, ZPush::GetAdditionalSyncFolders() can return integerIds as keys if requested (default as backendIds), do Backend->Setup() with backendIds in ChangesMemoryWrapper, backendfolderid needs to be set in SyncParameters unsetdata, allow Notes folders as additional static folders.
  ZP-849 Changes: - Move folders correctly with mapped and traditional profiles - Changed IIChanges->ImportFolderChange() to return a SyncFolder object to transport all ids. - Added logging to Zarafa importer and folder move operations.
  ZP-849 Fixed typos, removed unnecessary isset() checks.
  ZP-849 Several changes here: - Changed IImportChanges interface to use an SyncFolder object on ImportFolderDeletion, changed all implementing classes to work with the new parameter to allow clean rewriting of ids for backends. - Expose folderid <-> backend-folderid conversion in both directions via DeviceManager, saved in the ASDevice contentdata. - All folderids passed to the backend, are rewritten to the backend-folderids, where all processing operations are done (as is) on the new/short AS folderids. - Never save ASDevice data when doing Ping, as on hierarchy changes there will be race conditions between, e.g. FolderCreate and the running Ping request, where Ping potentially wins writing this information (risk of inconsistent AS folderids). The ASDevice is only changed because during hierarchy verification new folders get a new AS folderid. This is not used anywhere and really done on the following FolderSync operation.