Limit Lambda role permissions - avoid wildcard resources

As of now, Elastic Serverless Forwarder Lambda Role uses the following managed policies:
- AWSLambdaSQSQueueExecutionRole
- AWSLambdaKinesisExecutionRole
- AWSLambdaBasicExecutionRole

All the above roles have attached policies with wildcard Resource statements (i.e `"Resource": "*"`). This is not great from a security perspective, so we should review the permissions required and create ad-hoc roles/policies with the strictest permissions, where possible.