Use server side apply for deploying K8s manifests and replicate kubectl apply behaviour

[ptzianos]

At the moment we are using the typed interfaces for deploying resources which makes our code more complicated and brittle than it should be. We should instead use server side apply, along with the more dynamic interfaces that the Go K8s client offers so that we can replicate the kubectl apply behaviour by allowing the API master to figure out which field needs to be modified in case the object already exists instead of us having to handle the create/it's already there so instead do an update workflow

[ptzianos]

merged as part of #161