feat!: Added advanced logging configuration. Bump version of AWS provider to 5.32

[JoshuaLicense]

Description

Adds logging_config block for enabling advanced logging.

Motivation and Context

Closes #530

Breaking Changes

No

How Has This Been Tested?

• [x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
• [x] I have tested and validated these changes using one or more of the provided examples/* projects
• [x] I have executed pre-commit run -a on my pull request

[JoshuaLicense]

Could you please update this module and handle the cases when the user specifies custom log group then default log group should not be created?

Maybe there are other cases that should be considered. I would appreciate if you can think about this and update this PR.

My bad, thanks for the review. I've pushed some tweaks that handle the different log group scenarios better.	use_existing_cloudwatch_log_group	logging_log_group	aws_cloudwatch_log_group created
true	null	❌ retrieved from data source: "/aws/lambda/${var.lambda_at_edge ? "us-east-1." : ""}${var.function_name}"
true	populated	❌ retrieved from data source: var.logging_log_group
false	null	✅
false	populated	❌ retrieved from data source: var.logging_log_group

Also, maybe we need to update the log group in the outputs of the module if user specifies custom log group.

Existing data source is re-used so outputs should update appropriately.

[antonbabenko]

This PR is included in version 7.0.0 :tada:

[AndrewCharlesHay]

This causes breaks in Gov Cloud see #539

[github-actions[bot]]

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.