When a cluster is set to be redeployed due to a secret change with the changes to the ES setting (e.g., CPU requirement in the logstore), current implementation will recreate the es type which overwrites the certRedeploy status. This PR fixes the issue by keeping the status if the cluster is set to be redeployed.