Add support for containers-storage backend for container images

[hkadakia]

What would you like to be added:
Currently syft & grype look for certain locations for finding the container images. It works fine if the container image is built either via docker or podman as the images they build reside in certain locations and those are part of the supported sources here.

Images built using buildah though reside in different location (usually containers-storage) and when scanning using syft, it scans the remote image instead of the locally built image.

Why is this needed:
Need to add support for scanning images built using non-daemonize tool like buildah. Add a new source where syft can look for when scanning image locally before checking OciRegistry.

Additional context:

[willmurphyscode]

I just wanted to say this is still on our backlog, and we'd welcome contributions for it, but we haven't been able to prioritize it yet.

[bitfisher]

+1

[vit-zikmund]

This would be awesome, using the sockets / image save is also very inefficient regarding data moving. With containers-storage these are readily accessible using the containers/storage Go library, sometimes exposed into CLI with commands like podman image mount, which don't copy any data at all ❤