Fixed UpdateManagerSvc setting of remote pointer
When a some client registered to a condition that is generated by another object (algorithm, tool, ...), if they were not initialized in the right order, the target pointer in the client was not updated.
This MR fixes the problem, so the workaround Rec!1280 (closed) is not needed anymore.
FYI @sponce