fix: Give unique alarm_name to avoid collision when default and gunicorn both create the same alarm name.

[codyfletcher]

Keeps this issue from happening:

 Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # module.main.module.celery_worker_autoscaling.aws_cloudwatch_metric_alarm.service_cpu_high will be updated in-place
  ~ resource "aws_cloudwatch_metric_alarm" "service_cpu_high" {
      ~ alarm_actions             = [
          ...
        ]
      ~ dimensions                = {
          ~ "ServiceName" = "staging-gunicorn" -> "staging-default"
            # (1 unchanged element hidden)
        }
        id                        = "staging_cpu_utilization_high"
        tags                      = {}
        # (15 unchanged attributes hidden)
    }

  # module.main.module.celery_worker_autoscaling.aws_cloudwatch_metric_alarm.service_cpu_low will be updated in-place
  ~ resource "aws_cloudwatch_metric_alarm" "service_cpu_low" {
      ~ alarm_actions             = [
          ...
        ]
      ~ dimensions                = {
          ~ "ServiceName" = "staging-gunicorn" -> "staging-default"
            # (1 unchanged element hidden)
        }
        id                        = "staging_cpu_utilization_low"
        tags                      = {}
        # (15 unchanged attributes hidden)
    }

Plan: 0 to add, 2 to change, 0 to destroy.