publish images.txt for individual BB components

Feature Request

Why

Several Big Bang component deployments reference multiple container images. Currently only one images.txt artifact with all of the images required for Big Bang is provided. This does not easily allow for downloading only what is needed in embedded/edge environments, resulting in larger artifacts to download and transfer. Currently multi-image charts make for a manual process/unnecessary scripting to make that link.

The more detail here the better!

Proposed Solution

With each component, publish an images.txt artifact containing the image urls/versions used by the chart deployment.

Acceptance Criteria

• images.txt is automatically created for package releases using the standard package pipeline
• images.txt contains a list of repository:tag images (one on each line)
• images.txt contains images pulled from the Kubernetes cluster (not the running containers, but the image storage itself). You can look at Big Bang on how this is done.
• images.txt contains only the images from the package itself, and not the dependencies. You could use an exclusion list or do a two part capture (once after the dependencies are installed and once after the package is installed) to get the final images.txt.