Ensure that all CRD statuses are compatible with kstatus (used by Argo and Helm)

Argo Rollouts and Helm both use the kstatus library under the hood to wait for the readiness of custom resources before considering a deployment "healthy".

We should ensure that all custom resources follow the conventions expected by kstatus to indicate rollout progress, errors, and success. Unit and/or integration tests should be included that verify kstatus correctly considers rollouts in progress/failed/succeeded for every Temporal custom resource type.

This was originally captured in https://github.com/temporalio/temporal-worker-controller/issues/76 (Automatically wait-for-health before finishing Helm install/upgrade). There is also related discussion in https://github.com/temporalio/temporal-worker-controller/issues/198.

After this issue is closed, Argo Rollouts users should not need to use any custom Lua scripts to wait for CRD readiness.