some oci bundles created with 0.10.4 of uds-cli fails to deploy with 0.11.x version of uds-cli

[zachariahmiller]

Environment

Device and OS: MacOS and Linux
App version: 0.11.x
Kubernetes distro being used: k3d
Other:

Steps to reproduce

1. install 0.11.x version of uds-cli
2. run uds deploy k3d-core-slim-dev:0.22.0
3. run uds deploy swf-dev:0.2.1
4. bundle deploy with missing file on sonarqube

Note: repeat the above steps with 0.10.4 of uds-cli and the deployment will complete successfully. I have been able to reproduce the above scenario consistently and many times already.

Expected result

Bundle deploy is successful

Actual Result

Bundle deploy fails

Visual Proof (screenshots, videos, text, etc)

Severity/Priority

high

Additional Context

Tried clearing zarf and uds caches. This consistently fails with both the swf-dev:0.2.1 and k3d-swf-demo:0.2.1 bundles on deploying sonarqube. @Racer159 has seen it intermittently fail in the same manner on the gitlab-runner test bundle. This is sort of blocking some SWF work and is not trivial to roll back due to things like --no-tea that have been removed in the same version change in individual repos and uds-common. For SWF team its not the end of the world wince our main artifacts we produce for consumption are zarf packages so it only impacts CI and if growth were to try to use one of our demo bundles with the latest uds-cli. A bigger concern is that this may impact delivery with their bundles once they have updated to 0.11.x.

Its possible this issue was introduced by #622