The generated strings don't actually deserialize and serialize in the
generated string form so there's no gain to them.

There's still potential for races to the update, but that may be a
product of the JSON Merge that's generated by the Kubernetes client -
either way, there's a chance for a race and it should be mitigated.

Massaging some of the conditions for validated usages

kind create cluster --config ./dev/cluster.yaml
kubectl apply -f ./dev/dashboard.yaml

Construct a view on the policy that's summarized for the policy check to
act on with. There are some issues that may be introduced with this
approach and need to be better formed, however, I think this will get
this functionality off the ground.

We can't yet check for a usable configured state from updog, that'll
have to come later. For now, checking that it exists on disk is enough
to convince ourselves that we're in the right place.

This allows for the testing that's now present.

* Add logging to command execution.
* Increase, temporarily, memory of running pod.
* Update ListUpdate logic.