Remove reciprocal references from SQS Queues

[ben851]

Description

As a developer/operator of GC Notify, I would like to be able to deploy the notify infrastructure from scratch, and create dynamic environments.

Currently we are unable to do so due to reciprocal references in the SQS queues with the lambdas. (Chicken/egg scenario)

WHY are we building?

• BCP
• Deploy environments from scratch
• Reliability
• Agility

WHAT are we building?

Modify the reciprocal SQS references for these lambdas:

• notify_internal_tasks
• delivery-receipts
• ses_receiving_emails
• heartbeat
• lambda-admin-pr
• lambda-api
• lambda-google-cidr

VALUE created by our solution

We will be able to deploy environments from scratch, allowing for dynamic environments, increased agility, and BCP

Acceptance Criteria

• [ ] Terraform apply can deploy against a new environment
• [ ] Staging and Production are migrated with minimal impact

QA Steps

• [ ] Test against new environments
• [ ] Verify staging/production still work as expected

[ben851]

The SQS queue eks-notification-canada-cadelivery-receipts seems to be created outside of terraform (via celery I assume). We need to move this into TF and validate that celery doesn't care that it's already created.

[ben851]

Closing this issue as it was resolved in a different card