Don't abort typical synchronization if a connection cannot be created due to existing overlap
Currently typical synchronization has a validation step that aborts the whole diagram synchronization if there is even a single connection missing from the instance diagram that cannot be copied from the typical template because another instance-specific connection has been made to the same functional terminal where the template connection is supposed to be connected.
We want the synchronization to simply report these cases as WARNINGS and be able to continue with the rest of the synchronization.