feat(doks,doks-public) enable HA for Kubernetes control-planes

[dduportal]

• HA upgrade done through the UI because https://registry.terraform.io/providers/digitalocean/digitalocean/latest/docs/resources/kubernetes_cluster#ha specifies that the cluster would deleted and re-created if done through Terraform
• Job is disabled on infra.ci
• A local terraform plan states:

Note: Objects have changed outside of Terraform

Terraform detected the following changes made outside of Terraform since the last "terraform apply":

  # digitalocean_kubernetes_cluster.doks_cluster has changed
  ~ resource "digitalocean_kubernetes_cluster" "doks_cluster" {
      ~ ha             = false -> true
        id             = "8f6e486f-86e9-45d0-a52b-d5554c70f4ec"
        name           = "jenkins-infra-doks-hkuxfyvb"
        tags           = [
            "managed-by:terraform",
        ]
      ~ updated_at     = "2023-06-21 13:24:07 +0000 UTC" -> "2023-06-22 15:22:50 +0000 UTC"
        # (13 unchanged attributes hidden)


        # (2 unchanged blocks hidden)
    }

  # digitalocean_kubernetes_cluster.doks_public_cluster has changed
  ~ resource "digitalocean_kubernetes_cluster" "doks_public_cluster" {
      ~ ha             = false -> true
        id             = "c2ac8f9f-55e0-44d7-9524-2848fd6e3747"
        name           = "jenkins-infra-doks-public-hkuxfyvb"
        tags           = [
            "managed-by:terraform",
        ]
      ~ updated_at     = "2023-06-21 13:06:27 +0000 UTC" -> "2023-06-22 15:24:17 +0000 UTC"
        # (12 unchanged attributes hidden)


        # (2 unchanged blocks hidden)
    }


Unless you have made equivalent changes to your configuration, or ignored the relevant attributes using ignore_changes, the following plan may include actions to undo or respond to these changes.

──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

No changes. Your infrastructure matches the configuration.

we can merge and then re-enable the job