lxc-host-image-demo fail in runinstall_container_image on KF

Close for LL 12.0.1

The redefinition of IMAGE_NAME and IMAGE_LINK_NAME done for the Kingfisher images as opposed to having a separate h3ulcb-kf MACHINE configuration is indeed inconvenient when we want to grab an image out of the deploy directory.  ATM I don't see a way to avoid having either some special case for Kingfisher or trying to determine that suffix with some anonymous python.  I'll experiment a bit and see what I can come up with.  One wrinkle is that I don't believe there's currently an override or AGL_FEATURE that identifies we're building for Kingfisher and not plain ULCB.  Re-enabling the "kingfisher" MACHINEOVERRIDE in meta-agl-bsp/meta-rcar-gen3-adas/conf/include/rcar-gen3-adas.inc might be one approach, then we could use it in lxc-host-image-minimal.bb.  Any thoughts, ?

As an aside, note that rcar-gen3-adas.inc directly appends to IMAGE_INSTALL, which does mean that those packages will end up in both the host and guest images.  That will likely need to be changed to using something like one of the MACHINE_EXTRA variables, though there's an outstanding issue there if the packages are viewed as required in the host since the IC EG LXC images do not pull in packagegroup-machine-base ATM and we're setting NO_RECOMMENDATIONS.  Right now that's being worked around with e.g. a rcar3 specific IMAGE_INSTALL_append in lxc-host-image-demo.bb, but that's not going to be sustainable long-term if many targets have to be supported.