🐛 Fix container image resolve in v9

[czunker]

Now, the os providers tries to find a requested container image locally within the dcker daemon. When this doesn't work, it tries to find the image in a remote registry.

Fixes #1699

[czunker]

Works now for images present locally:

cnquery run container image debian:11 -c "container.image{*}" --verbose 
DBG using provider os with connector container
! using builtin provider for os
→ loaded configuration from /etc/opt/mondoo/mondoo.yml using source default
DBG found docker engine image sha256:54e726b437fbb2dd7b43e4dd5cd79b0181e96a22849b7fc2ffe934fac2d65440
DBG tar> load tar file into backend path=/tmp/mondoo.inspection3801697835

and remote:

cnquery run container image debian:10 -c "container.image{*}" --verbose 
DBG using provider os with connector container
! using builtin provider for os
→ loaded configuration from /etc/opt/mondoo/mondoo.yml using source default
DBG try to download the image from docker registry
DBG detected container image in container registry image=debian:10
DBG asset platform ids platform-ids=["//platformid.api.mondoo.app/runtime/docker/images/972a285e4630b87e839bdcc09cb6fad08956524397b4d3878a5b65a8e6c3fdee"]
DBG found valid container registry reference ref=index.docker.io/library/debian:10
DBG tar> load tar file into backend path=/tmp/mondoo.inspection3196368470
...