correct determination of a host's container images
correct determination of a host's container images

The same container image may be in use on multiple hosts. The
latest-map HostNodeID of a node in the ContainerImage topology is
therefore meaningless - it gets set to whatever host reported that
image last in the time window covered by the report. Hence using it as
a basis for mapping to hosts, as we did, a) fails to associate images
with all the right hosts (hence they are missing from the host details
panel), and b) causes that association to change semi-randomly (hence
the list in the details panel is unstable).

By contrast, the host topology parents of container image nodes is the
complete set of all hosts the image is used on. So making that the
basis for mapping fixes the problem.

The same technique - mapping based on host parents rather than
latest-map HostNodeID - also works for the other nodes we are mapping:
processes, containers and pods. So we might as well use it there
too. That's also what Map2Parent does in other topology renderers.

Fixes #2629.

kinvolk/scope,alban/scope,alban/scope,kinvolk/scope,weaveworks/scope,alban/scope,weaveworks/scope,kinvolk/scope,weaveworks/scope,weaveworks/scope,kinvolk/scope,alban/scope,weaveworks/scope,weaveworks/scope,kinvolk/scope,kinvolk/scope,alban/scope,alban/scope