This pull request introduces significant updates to the AWS remediation module, including enhancements to configuration flexibility, support for scheduled remediation, and compatibility updates for newer AWS provider and Lambda runtime versions. Below is a summary of the most important changes grouped by theme.

Configuration Enhancements

• Renamed lambda_zip to path_to_lambda_zip for clarity and updated references across README.md, main.tf, and variables.tf. [1] [2] [3]
• Changed remediation_options from a single object to a list of objects, allowing multiple remediation configurations. Updated associated validation rules. [1] [2]
• Added remediation_schedule_days and ssn_notification_topic_arn variables to support scheduled remediation and optional SNS notifications. [1] [2]

Scheduling and Event Handling

• Replaced the single EventBridge rule for Inspector findings with a dynamic schedule-based approach using remediation_schedule_days. Each schedule triggers remediation for the specified configurations.
• Added support for optional SNS notifications for remediation events if ssn_notification_topic_arn is provided. [1] [2]

Compatibility Updates

• Upgraded the AWS provider version requirement from ~> 4.0 to ~> 5.0 in versions.tf and examples/basic/terraform.tf. [1] [2]
• Updated the Lambda runtime from nodejs18.x to nodejs20.x in main.tf.

IAM Policy Adjustments

• Scoped IAM policies more tightly by replacing wildcard resources with specific ARNs for logs, SSM, and Inspector services. [1] [2]

Example Updates

• Updated the example in examples/basic/main.tf to reflect the new variable names, list-based remediation_options, and added scheduling configurations.

These changes improve the module's flexibility, security, and compatibility, while also introducing new features for automated and scheduled remediation.