Fix: when a RemoteObject receive a call, forward to related ObjectHosts.
Fix: when a RemoteObject receive a call, forward to related ObjectHosts.

When we detect that a RemoteObject received a call, it's a message
routing error. However because of object id collisions (their values
are defined by a counter in each process, so it's possible for
two objects from two different processes to end up
sending messages with the same objectid) we should also check if the
real destination object isn't an host of the RemoteObject before
dropping the message (resulting in an infinite wait for the caller).

This does not fix the object identification issue, it can only
be fixed by changing the design of the messaging protocol.

Change-Id: I599f761af7acda235365b071806caad1281e065c
Reviewed-on: http://gerrit.aldebaran.lan/78490
Reviewed-by: jmonnon <8898eaf233516e520f996a244ca8a12d20f948b1@aldebaran.com>
Reviewed-by: jlamotte <70353e7b0c7d18b7fc75605daf0ccba69fcd3222@aldebaran.com>
Tested-by: jlamotte <70353e7b0c7d18b7fc75605daf0ccba69fcd3222@aldebaran.com>

aldebaran/libqi,aldebaran/libqi,aldebaran/libqi