Add Support for JSONL.GZ Log Files in lambda-promtail Module

[samuelebstein]

Is your feature request related to a problem? Please describe.
GuardDuty publishes findings as logs with a “.jsonl.gz” suffix, but the lambda-promtail module only allows for “.log.gz” suffixed log files. This limitation means I have to create resources outside of the module to invoke the Lambda function, create the S3 event notifications, and add the relevant get object policy to the Lambda myself.

Describe the solution you'd like
I would like the lambda-promtail module to support different log formats, specifically allowing for “.jsonl.gz” files. This would enable the entire setup, including S3 event notifications and IAM policies, to be handled within the module, simplifying the setup.

Describe alternatives you've considered
I have considered creating additional resources outside of the module to handle “.jsonl.gz” files, but this adds unnecessary complexity -- though it is simple enough. Another alternative is modifying the existing lambda-promtail module locally, but this is not ideal for long-term maintenance and updates.

Additional context
Adding support for multiple log formats within the lambda-promtail module would streamline the integration with services like GuardDuty, which may publish logs in different formats. This enhancement would improve usability and reduce the need for additional configuration outside the module.