manifests that get removed from packages, appear to be left behind on subsequent updates

[GemmaClements]

Environment

Device and OS: Local Dev K3s Cluster (but also occurs on others)
App version: Zarf 0.77
Kubernetes distro being used: 1.34
Other:

Steps to reproduce

1. Create a Zarf Package with a Component manifest file i.e. simpleConfigMap - and deploy
2. Create second Component within the Zarf Package with another manifest to the same namespace i.e. simpleConfigMapTwo- and redeploy with new version
3. Either

• delete the first manifest and redeploy with new version
• or even completely remove the component and redeploy with new version

Expected result

To behave similar to a helm upgrade where the resources on cluster that were part of the chart, and in an upgraded version are removed, they are removed on cluster to realign to the chart structure/content

Actual Result

The old simpleConfigMap appears to be left on the cluster despite having been removed

Visual Proof (screenshots, videos, text, etc)

Severity/Priority

Low, but can be problematic when working with resources that could conflict like policies

Additional Context

Add any other context or screenshots about the technical debt here.