Enhance ability to get a full status of the deployed package and components

[GemmaClements]

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

Although, zarf package list provides what was "last" deployed which is create for checking the initial version, it does not necessarily provide much details regarding "deployment state" of the cluster regarding the currently deployed components.

Consider the following:

Deploy a package i.e. zarf package deploy --components=a,b
Run zarf package list, zarf package list, it shows you the package and both components a and b.

Deploy a new version of a package, but this time you only want to test component 'a' first so just run i.e. zarf package deploy --components=a
Run zarf package list, and this time it will list the new version, with only component a listed even though the 'b' component is still there its just on an older version.

Describe the behaviour you'd like

• Given you run an upgrade with any number of components
• When you run zarf package list (or a zarf package status? command)
• Then it should be possible to get a full status on each "component" deployed and the zarf package version they are deployed with

Describe alternatives you've considered

(optional) A clear and concise description of any alternative solutions or features you've considered.

Additional context

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

[brandtkeller]

Thanks for the issue and ultimately I agree. I explored this as part of some prune work that is being incorporated into the current enhanced state management proposal (See story 1).

Zarf takes a conservative approach for any operation that could delete a resource. So we believe that having an option to prune a component that is no longer being included in state to maybe solve for this?

Open to thoughts.