Azure Event Hub Namespace - Ensure the Azure Event Hub Namespace is zone redundant

[tdefise]

Describe the issue
It seems that there are no Checkov checks related to the best practice of making the Azure Event Hub "Zone-redundant" azurerm_eventhub_namespace

Examples

resource "azurerm_eventhub_namespace" "example" {
  name                = "example-namespace"
  location            = azurerm_resource_group.example.location
  resource_group_name = azurerm_resource_group.example.name
  sku                 = "Standard"
  capacity            = 2
  zone_redundant      = True

  tags = {
    environment = "Production"
  }
}

Version (please complete the following information):

• N/A

Additional context

This is a best practice as the all-active Azure Event Hubs cluster model with availability zone support provides resiliency against grave hardware failures and even catastrophic loss of entire datacenter facilities.

If an Event Hubs namespace is created in a region with availability zones, the outage risk is further spread across three physically separated facilities, and the service has enough capacity reserves to instantly cope up with the complete, catastrophic loss of the entire facility.

When a client application sends events to an Event Hubs without specifying a partition, events are automatically distributed among partitions in the event hub. If a partition isn't available for some reason, events are distributed among the remaining partitions. This behavior allows for the greatest amount of up time.

Note that for existing Azure Event Hub Namespace, this will re-create the resource