[Bug] Cannot enable custom tls configuration for tcp synthetic monitor

[jeffbeagley]

Describe the bug
When deploying a synthetic monitor with type set to tcp, and ssl_verification_mode set ,there is no way to enable "custom tls configuration" which will then not respect the ssl_verification_mode. I also manually enabled it via console, and terraform detects no drift.

To Reproduce
Steps to reproduce the behavior:

1. TF configuration used '...'

resource "elasticstack_kibana_synthetics_monitor" "tcp_monitors" {
  name              = "some_name"
  tags              = var.tags
  space_id          = var.space_name
  enabled           = true
  schedule          = 3
  private_locations = var.locations
  alert = {
    status = {
      enabled = true
    }
	tls = {
	  enabled = true
	}
  }

  tcp = {
    host = "tcpendpoint:port"
	  ssl_verification_mode = "certificate"
  }

}

2. TF operations to execute to get the error '...' [e.g terraform plan,terraform apply, terraform destroy]
   terraform apply
3. See the error in the output '...'
   Within the UI, "Use Custom TLS Configuration" is disabled

Expected behavior
When Custom TLS Configuration is enabled, then certificate monitoring is enabled

Screenshots

Versions (please complete the following information):

• OS: Linux - Ubuntu
• Terraform Version 1.13.1
• Provider version 0.9
• Elasticsearch Version 9.1