Add UDS CLI OCI repo detection superpowers

[docandrew]

Is your feature request related to a problem? Please describe

There's no easy way to inspect an OCI repo and determine whether it contains a Zarf package, or a UDS package, or a UDS bundle, or a Helm OCI chart, etc. You can curl the OCI URL endpoint and manually inspect layers looking for indicative files, but this is error-prone and time-consuming.

Describe the solution you'd like

I propose the addition of capabilities to uds inspect to allow it to determine what type of image/package is contained in an OCI repo. Initially, being able to determine if a Zarf package is a UDS package or not would be helpful.

Later, detecting other OCI image types such as Helm charts, Snaps, and even some types of VM images would be a powerful addition to UDS CLI as well.

[bburky]

Related:

Zarf uses a specific application/vnd.zarf.config.v1+json mime type on the config layer. This allows easily identifying a zarf package from its OCI metadata.

Uds-cli however, uses a application/vnd.zarf.layer.v1.blob mime type for it's config (this is arguably incorrect, this is not supposed to be used for config, it's also used for all the layers). So you can't really identify if your OCI thing is a UDS bundle from the obvious metadata. (for now, you can look for a uds-bundle.yaml layer, but as this issue says, this is tricky and maybe error prone)

In addition to maybe improving some CLI commands like uds inspect as this issue requests, I'd suggest changing the config mime type for UDS bundles to something UDS bundle specific?