proper scoping for docx redline import (bnc#821804)

propagateCharacterPropertiesAsSet sends the properties only when ending
a text run (or maybe starting another one, I'm not quite sure), so it breaks
ordering by sending them later then expected (although it worked in many cases).
It's a question if propagateCharacterPropertiesAsSet is to be used by anything
actually, since it seems rather broken to use it in the ooxml frontend.
Using sendPropertiesWithId sends the properties properly at the right time,
as one would expect. I don't know why dmapper can't simply handle this on its
own, as I think it does handle entering and leaving other elements, but
spending more time on it with this overdesigned abomination, oh well.

Change-Id: Ie36c5f933ea3e6d789ea8f9e4ee3b60a5d1c920c
display paragraph format redline also as 'formats' rather than empty string

Change-Id: I5ae5ce80fdb453fdf5de54c691de4cd0b88ad7f6
handle scope of w:pPrChange and w:rPrChange properly (bnc#821804)

Redlines changing formatting of runs and paragraphs are valid for the entire
run/paragraph, not just their existence in the XML. So store them
in the matching contexts, which will care of it, instead of the endtrackchange
stuff.

Change-Id: Ie583e4be14e8df95829852bfbbbe25aa0684f02e
report ParagraphFormat redline type in UNO too

Change-Id: I0cf7586a154ca73ce64a2328ff8df1858e2290ac
docx redline import test (bnc#821804)

Change-Id: I09749037deb44c0cd74b28af226dd4b3e34ee0d1