oxcmsg: Implementation for partial UserDNs in ModifyRecipients call

When Outlook passes some value in RecipientRow.prefix_size, then
we should restore the full legacyExchangeDN in recipient_x500name
using szDNPrefix we supplied to Outlook during Connect op.

Signed-off-by: Kamen Mazdrashki <kmazdrashki@zentyal.com>
oxcmsg: Resolve x500dn back to sAMAccountName due to SOGo limitations atm

Despite comments, SOGo expects message_recipient->username to be
the sAMAccountName for the recipient.
Thus resolving parital x500dn to a full one brakes the backend.
Utill this is fixed, this patch is a reasonable fix for that limiatation
Merge pull request #99 from openchange/kamenim/modify-recipients-partial-x500dn-impl

RopModifyRecipients partial x500dn implementation
emsmdbp/table_get_row_props: Check for OOM
emsmdbp/table_get_row_props: test retvals as mapistore_error value

rather than treating the value as boolean expression
oxcfxics: Prototype oxcfxics_fill_transfer_state_arrays() to return status code
oxcfxics: Check for errors in oxcfxics_fill_transfer_state_arrays() and handle accordingly
emsmdbp_object: Return MAPISTATUS and check for distinct error types
emsmdbp_object: emsmdbp_object_open_folder_by_fid() to return MAPISTATUS

And also handle different kinds of error properly in implementation.
enum mapistore_error is mapped to enum MAPISTATUS for instance
oxcfxics: Check for table_set_columns() errors in oxcfxics_push_messageChange_attachments
oxcfxics/SyncImportHierarchyChange: Fix MAPISTATUS error handling
oxcfxics/SyncImportMessageMove: Handle MAPISTATUS error and print out the error
provisioning: Print out more descriptive failure when LocalFree busy create fails
oxcstor/Logon_Mailbox: OPENCHANGE_RETVAL_IF() expect bool as a flag - fix that
oxcfxics: Fix memory context allocation check
oxomsg/handle_message_relocation: Use MAPISTATUS to check for errors instead of mapistore_error

Also, polish the error message in the log a bit, so we have
info which is the failing FID and what the error is.
oxcfxics: Relax error checking a bit to restore previous behavior

As blaxter suggested, we don't have a sane approach to test
what would happen if we like really fail here
So for now I am returnint old behavior partially until
we get more time to test it
provisioning: Get back to print function name and fix double __LINE__ printing
oxcfxics: Fix log message typo
mgmt_messages: Fix wron error type - mapistore_error is expected