Extends comments to clarify that these rules apply only to logs

[jsubirat]

Relevant information

This PR simply adds more explanatory comments as to where the data used by the affected rules comes from. For these rules, the Logs Pipeline pre-enriches the logs with some attributes like the aws.Arn, optionally an entityId and an entity name (aws.lambda.FunctionName or aws.alb.loadBalancer, for instance) so that entity synthesis can work. More information can be found here: https://docs.newrelic.com/docs/logs/logs-context/aws-logs-in-context/ (still being reviewed)

Checklist

• I've read the guidelines and understand the acceptance criteria.
• The value of the attribute marked as identifier will be unique and valid.
• I've confirmed that my entity type wasn't already defined. If it is I'm providing an explanation above.

[otaviocarvalho]

Linking our internal CDD for future reference. I have took a long-time to realize those AWS rules were not owned by Infra but Logs instead: https://newrelic.atlassian.net/wiki/spaces/TDP/pages/3670966562/CDD+-+Entity+Synthesis+for+Infra+AWS+entities+out+of+Logs