Update OSCAL/Validations to handle ambient mesh/workloads for Istio

[mjnagel]

Related to #681

Our current OSCAL/Validations check for a sidecar on every workload and a specific label for istio injection. With the switch to Ambient sidecars will not be present on all workloads. The validation should be updated to handle both sidecar and ambient workloads, and allow for either to pass the validation.

Changes will end up being to these:

• https://github.com/defenseunicorns/uds-core/tree/main/compliance/validations/istio/all-pods-istio-injected
• https://github.com/defenseunicorns/uds-core/tree/main/compliance/validations/istio/all-namespaces-istio-injected

[mjnagel]

Based on current path forward this work is being deprioritized. We will need to follow up to make sure our current compliance CI does not fail here - for the time being we could either modify the validation to always pass or just disable the compliance workflows.

[noahpb]

No changes to compliance results as of yet. This could change as we gradually opt packages in uds core in to ambient.

[mjnagel]

Path for this for now is to just disable the oscal/compliance workflows.