fix: Use local log_group throughout, fixing log configuration with Lambda@Edge.

[theherk]

Fixes #650 and #665.

Description

Motivation and Context

This allows module implementations using lambda_at_edge = true to actually log to Cloudwatch.

Breaking Changes

This will cause changes for users using lambda_at_edge = true, but is is a fixing change.

How Has This Been Tested?

• I have verified the changes in my infrastructure.

• I have executed pre-commit run -a on my pull request

 terraform-aws-lambda ᐅ pre-commit run -a Terraform fmt............................................................Passed Terraform wrapper with for_each in module................................Passed Terraform docs...........................................................Passed Terraform validate with tflint...........................................Passed Terraform validate.......................................................Passed check for merge conflicts................................................Passed fix end of files.........................................................Passed trim trailing whitespace.................................................Passed mixed line ending........................................................Passed 

[github-actions]

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

[github-actions]

This PR was automatically closed because of stale in 10 days

[theherk]

Cool, another PR closed out of hand because these repositories are mostly unmonitored. 👍

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.