feat: Add variable create_lambda_permission in notification module

[maxrabin]

Description

In the Notification module create a new variable a new create_lambda_policy that functions similar to create_sqs_policy and create_sns_policy

Motivation and Context

I define and manage my Lambda Policy separate from the Terraform where I manage my S3 Notifications. I don't want this module to force me to manage the Lambda policy here.

Fixes #301

Breaking Changes

I think that migrating aws_lambda_permission.allow from a single to a count this will cause the Resource to be recreated.
This can be avoided by performing terraform state mv

There are 3 types of notifications, and this change brings Lambda in line with SQS and SNS that support create_sqs_policy and create_sns_policy

How Has This Been Tested?

• I have updated at least one of the examples/* to demonstrate and validate my change(s)
• I have tested and validated these changes using one or more of the provided examples/* projects

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

[antonbabenko]

Good idea, but let's rename var from create_lambda_policy to create_lambda_permission since Lambda has permissions, but SNS/SQS has policies.

[antonbabenko]

This doesn't seem like a breaking change, since for_each is used, so we are good.

[maxrabin]

This doesn't seem like a breaking change, since for_each is used, so we are good.

I realized you're right!

[maxrabin]

Good idea, but let's rename var from create_lambda_policy to create_lambda_permission since Lambda has permissions, but SNS/SQS has policies.

I renamed it to create_lambda_policy

[antonbabenko]

This PR is included in version 4.4.0 🎉

[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.