[BUG] Manifests do not support labels about wadm HOT 3 CLOSED

If our goal is Kubernetes interop for these, I think at a minimum we'd want to support the same rules Kubernetes does per their guidelines.

For some concrete examples of what these look like in the wild, Helm has a section in their best practices guidelines on what you might see from a helm-based application deploy

from wadm.

To make the case more concrete, in order for the wasmcloud-operator to more fully interoperate with commonly used Kubernetes tooling, such as Helm or ArgoCD, that have defaults built-in for using labels we really do need the ability to persist labels as part of the manifest.

from wadm.

Oh does this fail the validation check when you add in a label @protochron ? This is a fairly easy add. What kinds of naming requirements would you like to enforce

from wadm.