Developer sees that the last SHA used in a plan is applied when merging

[ohrite]

Summary

This PR sets up terraform to deploy the most recently planned SHA when merging a PR.

Relates to #37

Type of change

• New feature
• Bug fix
• Documentation
• Configuration

Post-merge actions

Monitor terraform apply

[github-actions]

Terraform plan in iac/
With variables: image_tag = "c3e2e1412574a59669d23912bd37c1201e4cbf17"

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

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:

  # google_cloud_run_v2_service.cal-bc-staging will be updated in-place
!~  resource "google_cloud_run_v2_service" "cal-bc-staging" {
-       client                  = "cloud-console" -> null
        id                      = "projects/cal-itp-data-infra-staging/locations/us-west2/services/cal-bc-staging"
        name                    = "cal-bc-staging"
#        (32 unchanged attributes hidden)

!~      template {
#            (10 unchanged attributes hidden)

!~          containers {
!~              image          = "us-west2-docker.pkg.dev/cal-itp-data-infra-staging/ghcr/cal-itp/cal-bc/cal-bc:development" -> "us-west2-docker.pkg.dev/cal-itp-data-infra-staging/ghcr/cal-itp/cal-bc/cal-bc:c3e2e1412574a59669d23912bd37c1201e4cbf17"
-               name           = "cal-bc-1" -> null
#                (6 unchanged attributes hidden)

#                (10 unchanged blocks hidden)
            }

#            (2 unchanged blocks hidden)
        }

#        (2 unchanged blocks hidden)
    }

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

📝 Plan generated in Terraform Plan #62