feat(alerts): New KubePdbNotEnoughHealthyPods alert

[skl]

Fixes #1028

[paulajulve]

[skl]

On hold, pending internal trial (~30 days).

[skl]

FYI test deployment shows that I may need to revert part of #1013, which is causing an error with our internal pipeline:

time="2025-03-25T14:28:28Z" level=error msg="bad recording rule name" error="recording rule name does not match level:metric:operation format, must contain at least one colon" file=output/mimir/dev-us-central-0.yaml rule=windows_pod_container_available ruleGroup=windows.pod.rules
time="2025-03-25T14:28:28Z" level=error msg="bad recording rule name" error="recording rule name does not match level:metric:operation format, must contain at least one colon" file=output/mimir/dev-us-central-0.yaml rule=windows_container_total_runtime ruleGroup=windows.pod.rules
time="2025-03-25T14:28:28Z" level=error msg="bad recording rule name" error="recording rule name does not match level:metric:operation format, must contain at least one colon" file=output/mimir/dev-us-central-0.yaml rule=windows_container_memory_usage ruleGroup=windows.pod.rules
time="2025-03-25T14:28:28Z" level=error msg="bad recording rule name" error="recording rule name does not match level:metric:operation format, must contain at least one colon" file=output/mimir/dev-us-central-0.yaml rule=windows_container_private_working_set_usage ruleGroup=windows.pod.rules
time="2025-03-25T14:28:28Z" level=error msg="bad recording rule name" error="recording rule name does not match level:metric:operation format, must contain at least one colon" file=output/mimir/dev-us-central-0.yaml rule=windows_container_network_received_bytes_total ruleGroup=windows.pod.rules
time="2025-03-25T14:28:28Z" level=error msg="bad recording rule name" error="recording rule name does not match level:metric:operation format, must contain at least one colon" file=output/mimir/dev-us-central-0.yaml rule=windows_container_network_transmitted_bytes_total ruleGroup=windows.pod.rules
time="2025-03-25T14:28:28Z" level=error msg="bad recording rule name" error="recording rule name does not match level:metric:operation format, must contain at least one colon" file=output/mimir/dev-us-central-0.yaml rule=kube_pod_windows_container_resource_memory_request ruleGroup=windows.pod.rules
time="2025-03-25T14:28:28Z" level=error msg="bad recording rule name" error="recording rule name does not match level:metric:operation format, must contain at least one colon" file=output/mimir/dev-us-central-0.yaml rule=kube_pod_windows_container_resource_memory_limit ruleGroup=windows.pod.rules
time="2025-03-25T14:28:28Z" level=error msg="bad recording rule name" error="recording rule name does not match level:metric:operation format, must contain at least one colon" file=output/mimir/dev-us-central-0.yaml rule=kube_pod_windows_container_resource_cpu_cores_request ruleGroup=windows.pod.rules
time="2025-03-25T14:28:28Z" level=error msg="bad recording rule name" error="recording rule name does not match level:metric:operation format, must contain at least one colon" file=output/mimir/dev-us-central-0.yaml rule=kube_pod_windows_container_resource_cpu_cores_limit ruleGroup=windows.pod.rules
mimirtool: error: 10 erroneous recording rule names, try --help

The windows recording rules do not follow the correct name conventions.

[skl]

This removes windows rules from the default build, see this comment where I was previously concerned about this change.