Wrong status value propagated to external resources if changed while pulling

In some specific cases the status of an user on an external resource could change remotely. If, simultaneously, some other attribute is changed and a propagation is fired the wrong status is propagated on the external resources.

For example, if an active (on syncope) user on resource-pull changes its surname, email and status (set to disabled) and a pull is fired, a propagation on some target resources occurs, depending on email and/or surname mapping. Propagation status is wrong, for example if pulled "disabled" the user is propagated active, i.e. _ENABLE_ attribute is set to false.