proposal: command to install spin-operator into a kubernetes cluster

[bacongobbler]

@michelleN raised a question during today's show and tell: do we want to grant spin k8s the ability to install spin-operator and all its dependencies into a Kubernetes cluster that does not have those systems installed? Why or why not?

[endocrimes]

I don't think so - We don't want to maintain a Kubernetes Packaging Tool (and kubectl apply -f https://github.com/spinkube/spin-operator/releases/v1.0.0/static-manifests.yaml would be a more understandable experience if we wanted something similar)

We may want something to generate SpinAppExecutors for a provided runtimeClassName?