chore: UDS CLI Bundle "v2" design

[Racer159]

Describe what should be investigated or refactored

Bundles have been a great way to reseal Zarf packages and their configuration alongside dependency packages for specific environments but as we have worked with the bundle format more, there have been some limitations that need to be addressed to scale well going forward. Namely:

1. Bundles today define dependencies in an entirely linear relationship meaning that for larger bundles you must wait for each Zarf package to be deployed one after the other when technically this is not required in most cases.
2. The current bundle format is not fully OCI spec compliant and there have been enhancements to the OCI specification that we should consider implementing to prevent layers from being mishandled in certain registry implementations.
3. Bundles today are able to manipulate Zarf packages in ways that Zarf as a CLI cannot support - this make maintenance more difficult and creates Zarf packages that can't be deployed with Zarf.

We should create a new design that addresses these concerns.

Links to any relevant code

https://github.com/defenseunicorns/uds-cli/tree/main/design-docs
https://github.com/defenseunicorns/uds-cli/blob/main/uds.schema.json

Additional context

This design will also need to handle migrations given the large install base of bundle v1 - this can and should be influenced by the work Zarf is doing in this area around zarf-dev/proposals#52 and zarf-dev/proposals#49