On sync with remote KB, keep TIPPs where coverage data is incompatible

Value:
When syncing with a remote knowledgebase, TIPP/resource should be brought into mod-agreements even where the coverage data is not compatible (specifically coverage end is before coverage start date), but the incompatible coverage data should not be populated into the resource. This means that libraries get as much information as possible from the remote KB, while not bringing in coverage data that is self-obviously incorrect