Updating to meet current lambda config

[ianbender]

Are there any dependencies (software or human) that need to be addressed before this PR is merged?

What ticket(s) or other PRs does this relate to?

https://linear.app/highwing/issue/FOUND-62/remove-legacy-broker-suite-terraform-code

What was the problem or feature?

Tearing down the old Broker Suite infrastructure and terraform folder.

What was the solution?

The current state of this module is no longer in use. Updating to the lambda_engine module that is now being used throughout the Broker and Carrier Suite.
https://github.com/highwingio/broker-suite/tree/main/terraform/modules/lambda_engine

• Security Impact has been considered (if yes please describe)
• Network Impacts have been considered (if yes please describe)

Where does this work fall on the Good - Fast spectrum?

Any additional work needed as a result of merging this PR (deploy steps, other PRs, etc.)?

[plukevdh]

Didn't realize we had our own internal module. Thought we just used the main TF/AWS module. 👍🏻

[ianbender]

Didn't realize we had our own internal module. Thought we just used the main TF/AWS module.
@plukevdh Technically both are true. The BS lambdas use the terraform/module/lambda_engine module, which uses the TF/AWS module. And now I'm just moving that out to public access.