dmsmdbp_object: emsmdbp_folder_get_folder_count() to return MAPISTATUS

Prevously, this function was returning something in between
mapistore_error and MAPISTATUS - depending on input data.

Callers of this function though expect a MAPISTTATUS
oxctabl: Remove unnecessary initialization - row blow is already initalized
emsmdbp_object: Check both PR_DISPLAY_NAME_UNICODE and PR_DISPLAY_NAME
for folder Display Name

Prevously, if we get the name as PR_DISPLAY_NAME prop tag value,
we weren't able to figure out what the name is ever
emsmdbp: Fix PidTagSourceKey creation for a message - messageID should be used
emsmdb: Remove folderID field from emsmdbp_object_message - not used anywhere
sz32/openchangedb: Map PidTagMid to "PidTagMessageId"

Historycally, PidTagMid has always been stored as "PidTagMessageId" attribute
sz32/openchangedb: Mapi PT_STRING8 type to PT_UNICODE when mapping PitTag's

This basically reintroduce commit 3fbf1b9cbb479a645dbde9afcd25fbda666f0d1e
but with different wording and without changing line endings
openchangedb: get_parent_if() should return error when input fid is not found
provosition/mailbox: Don't lowercase Organization and OU names for Free/Busy provision

Openchange compares object names in case sensitive mode
Hence, provisioned folder name is going to be not-searchable
with restrictions for instance
emsmdbp: refactor functions searching for either org or group
emsmdbp_object: sanity and error checks
oxcfxics: mark log messages for synccontext with 'syncstream'
emsmdbp/provision: Handle errors during Freebusy provisioning

This patch doesn't remove 'abort()' call in case of failure,
but instead print more information about the failure.
I have seen failures with this in cases when GlobalCount counter
gets messed up for some reason. In such cases, we better
abort as the state is messed up pretty badly and DB should be
fixed manually
Merge pull request #101 from Zentyal/kamenim/zs-3.2-freebusy-and-fixes

zs-3.2: Freebusy and other fixes along the way