Feat: add service account support

[nimish-ks]

How to test things locally:

• Start a new kubernetes cluster - minikube start
• Apply the CRD - kubectl apply -f kubectl apply -f crd-template.yaml
• Create the Phase service token v2 secret

kubectl create secret generic phase-service-token \
  --from-literal=token=<TOKEN> \
  --type=Opaque \
  --namespace=default

• Apply the following CR:

apiVersion: secrets.phase.dev/v1alpha1
kind: PhaseSecret
metadata:
  name: example-phase-secret
  namespace: default
spec:
  phaseApp: "example-app" # The name of your Phase application
  phaseAppEnv: "development" # OPTIONAL The Phase application environment to fetch secrets from
  phaseAppEnvPath: "/" # OPTIONAL Path within the Phase application environment to fetch secrets from
  phaseHost: "http://localhost" # OPTIONAL - URL of a Phase Console instance
  authentication:
    serviceToken:
      serviceTokenSecretReference:
        secretName: "phase-service-token" # Name of the Phase service token with access to your application
        secretNamespace: "default"
  managedSecretReferences: # Managed secrets in Kubernetes that Phase will sync secrets with
    - secretName: "my-application-secret" # Name of the managed secret in Kubernetes that will be consumed by your application
      secretNamespace: "default"

• In python venv - install all dependencies
• Run the operator in dev mode - kopf run src/main.py
• Watch for secrets being created - watch kubectl get secrets
• Verify that the secret has been synced - kubectl get secret my-application-secret -o yaml

[cloudflare-workers-and-pages]

Deploying helm-repo-kubernetes-secrets-operator with    Cloudflare Pages

Latest commit:	cdb7b78
Status:	✅  Deploy successful!
Preview URL:	https://bd5ad4ae.helm-repo-kubernetes-secrets-operator.pages.dev
Branch Preview URL:	https://feat--add-service-account-su.helm-repo-kubernetes-secrets-operator.pages.dev

View logs