RTF import: fix spurious page breaks at doc end (related: rhbz#1065629)

When a document ends with \sect it's possible that a spurious page break
is created.  In fact the spurious page break is always created by the
RTF importer, sometimes it is deleted again by
DomainMapper_Impl::RemoveLastParagraph() and sometimes not.

It is created because on the final \sect RTFDocumentImpl::sectBreak()
still calls startSectionGroup(), and the popState() for the \rtf1 group
then calls sectBreak() another time.

To prevent this, do not call startSectionGroup() from sectBreak() but
instead from setNeedSect(), and ensure that it is called as soon as
anything after \sect is read.

One unit test fails because the \page is not handled properly: the
conversion to \skbpage \sect \skbnone is not correct, because the \skb*
keywords are an exception and affect the \sect that precedes them, not
the following one; sending the \skbpage later unfortunately requires
additional cleanup later.

Change-Id: I3c1a3bceb2c8b75bbecdc748170562451ce5f5c3
RTF import: add unit test for page break in continuous section

Change-Id: I8b766aa61b1121f9b7068f5ccbdc24ef97253432
RTF import: fix paragraphs in header/footer

Change-Id: I91f04cad7a39428ce6f9555d18b974f0d45181f7
writerfilter: salvage a field parameter parsing train wreck

Field parameters get horribly maimed by lcl_ExtractParameter which
clearly has never worked in its 7 years of existence (and looking at the
inanity at the call sites makes one wonder what the author was smoking).

The format is actually quite annoying, since spaces between parameters
are optional.

The old RTF filter was at least able to parse "PAGEREF bookmark" fields,
so this fixes such regressions (related: rhbz#1065629).

Change-Id: I9b2e32c3c7264be0fc1077cb8fb3f1bc5c1955bb
fdo#47811: fix setPropertyValue("Name") of Database fieldmaster

This one is assigning to the wrong pType variable.

(regression from CWS swwarnings)

Change-Id: I9a74734d22313f215ed69c9a57edf7eb035736ea
fdo#47811: RTF import: fix Database field content

1. the Database field master does not have a "Content" property
2. SetFieldContent was called once for every chunk of text in the field
   result, always overwriting the previous value; accumulate the text.

Change-Id: I63cfda19e2e416c52d100d9071796305a5d813c6