reordered member variables for 4 byte alignment

Change-Id: Iaae7689d1ed3c74e261fcc90fa88b5521468e376
(cherry picked from commit dd902b8e256867b5d5fed06b52995f14d969f67d)
just beautify this a little

Change-Id: Ibd7da12d88ec8e965f652499f7e7e32f81bd8ccc
(cherry picked from commit 44b4973fbd0f190906f36321b31215d80b363d52)
prepared XMLPropertyMapEntry with mbImportOnly flag

Change-Id: Id5a54a591a42c836884af1fd09dc055f2fce6db5
(cherry picked from commit 9dd7ee88bd9835ae2bae36093100fcd651fd3aeb)
added bool bForExport parameter to XMLPropertySetMapper ctor

Set to true for export, false for import. If export true, an
XMLPropertyMapEntry with mbImportOnly==true is not added to the
mappings. This to be able to have more than one mappings for import
(for example a current extension namespace and the future namespace
proposed to the ODF-TC, or corrected typos in element or attribute
names), but map only to one entry on export, of course.

Change-Id: Ia01ea949c88eda2f8a6c10f51c59e35e7abdcaf3
(cherry picked from commit ebc1b2fe50c7ed1002ed8431410b8e2ac6e795b9)