Kubernetes apiVersions are mostly forward/backward
compatible, so for cases where we know it's safe, we
auto-alias the apiVersions so that the engine does not
force a replacement when a resource is updated to a
compatible apiVersion.

Force a replacement for resources with the
extensions/v1beta1 apiVersion when the apiVersion
changes.

Reverse the force-replace change for e/v1b1 apiVersions,
and instead store the apiVersion for the orginial create as
an annotation on the k8s resource. The await logic uses
this annotation to choose the correct logic path.

Check that e/v1b1 Deployment can update successfully after
changing the apiVersion.