#8 Move SSM parameter definitions to bootstrap terraform

[jayhill]

We had a chicken-and-egg issue where during our GH Actions workflows, SSM parameter validation would be checking for the existence of parameters before Terraform created them.

By moving parameters to the bootstrap process, they will be set in advance and values can be set interactively without having to go to the AWS console or use the CLI.

[github-actions]

Terraform Dev Plan 📋

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  - destroy

Terraform will perform the following actions:

  # module.main.aws_ssm_parameter.alert_email will be destroyed
  # (because aws_ssm_parameter.alert_email is not in configuration)
  - resource "aws_ssm_parameter" "alert_email" {
      - arn             = "arn:aws:ssm:us-east-2:253137917187:parameter/jaildata/alert-email" -> null
      - data_type       = "text" -> null
      - description     = "E-mail address for JailData alerts" -> null
      - id              = "/jaildata/alert-email" -> null
      - name            = "/jaildata/alert-email" -> null
      - tags            = {} -> null
      - tags_all        = {} -> null
      - tier            = "Standard" -> null
      - type            = "String" -> null
      - value           = (sensitive value) -> null
      - value_wo        = (write-only attribute) -> null
      - version         = 1 -> null
        # (2 unchanged attributes hidden)
    }

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

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

Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.