Feat: Show packages that did not require the cluster during deploy when running zarf package list

[AustinAbro321]

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

Users have reported that it's often confusing to figure out if a Zarf package has been deployed in an environment if the Zarf package doesn't effect the cluster. In this case the package won't show when zarf package list is run. One instance we've heard this reported is when one is deploying packages with infrastructure as code.

Describe the solution you'd like

• Given I have connectivity to a cluster and have a package that doesn't affect the cluster
• When I run zarf package deploy
• Then my package is tracked in the cluster or
• Given I don't have connectivity to a cluster and have a package that doesn't affect the cluster
• When I run zarf package deploy
• Then I get a warning message that my package will not be tracked in the cluster

Questions on implementation

• It still may not entirely truthful unless we error out when unable to connect to a cluster. This can't be the default behavior, but should we add flags or items in the package schema to make tracking the package required?
• Is it a good idea to add this feature? Or would it be confusing to users to see packages that aren't actually in the cluster

Describe alternatives you've considered

We could continue to not show packages that don't effect the cluster.