Fixed spurious CBLDocumentChange.inConflict value

When a previously nonexistent document is created via a pull replication,
the inConflict flag was mistakenly getting set (because technically a new
branch of the document is being created; it just happens to be the first
one.)
Fixes #243