Is your feature request related to a problem? Please describe.

When interacting with zarf packages in a CI env, I would like to be able to easily extract the underlying containers used in the making of a given zarf package. This will be valuable for thoroughly scanning image components.

Describe the solution you'd like

• Given I have a zarf package with a list of images that I would like to provide container scanning artifacts for
• When I zarf package inspect <some-remote-package> --list-images
• Then I can see the full list of images in the zarf package so that I can provide scan artifacts for each image.

Describe alternatives you've considered

Inspecting a package and piping that output to yq to filter out just the images.zarf package inspect <some-remote-package> 2>&1 | tee image_list.yaml

Additional context

Add any other context or screenshots about the feature request here.