Fixed another spurious CBLDocumentChange.inConflict value

The logic for setting inConflict in -forceInsert:… was broken. It needs
to check whether the local revision it's going to add a child of is
currently a leaf or not.
Fixes #243.