Support skipping an entity on field import errors

Problem/Motivation

Currently, we support skipping a specific field when an error occurs during field transformation, while continuing with importing the remaining fields for the entity. There are cases, however, where we want to skip importing the entire entity with or without logging the error. Due to not always having control over the remote system, we may not be able to prevent an error from happening in cases where the cause of the error should lead to skipping the entity i.e. expected behavior - thus the option to not log it.