BAU: Migrate all lambdas to endpoint-module-v2

[whi-tw]

What

endpoint-module is quite inefficient, as it does a number of data queries internally. Additionally, all of its' logic is implemented in endpoint-lambda.

I've migrated all our lambdas over to use endpoint-module-v2.

This new module has the following benefits:

• It does not do data queries internally, instead requiring these values to be passed in. This reduces the time for apply, as we will no longer needlessly re-request the same information over and over again
• It uses endpoint-lambda as the lambda-creation engine, which means we have configuration in only one place
• It exposes the endpoints required to create a openapi-backed API Gateway in future.

Additionally, I've stopped looking up the account alias and the slack SNS topic within each component, instead retrieving them from shared state. This further reduces the number of data lookups.

Finally, I've shifted dynatrace.tf out of the individual components, and into the parent directory, and have symlinked it in to the individual directories, removing the possibility of different modules getting out of sync.
This is the same pattern as we use with versions.tf

How to review

• Code Review
• Deploy it to a dev environment and check it works okay

[github-actions]

Java Tests Skipped

No Java files were changed in this pull request. Java tests will be skipped¹.

Any Java files that are changed in a subsequent commit will trigger the Java tests.

Footnotes

1. These tests will still show as passing in the PR status check, but will not actually have run. ↩