Add aws.requestId to Log Message if the lambda_request_id is found

[david-a-jetter]

This copies the value that is set in aws.lambda_request_id to aws.requestId on the log message dictionary that is ultimately submitted to the New Relic Logs API.

The reason for this is to support a use case leveraging Insights dashboards that combine data from AwsLambdaInvocation and Log NRQL queries along with the Filter New Relic One dashboards by facets. The idea being to:

1. Build a query / chart that fetches matching Invocations
2. Leverage the filtering feature to filter the dashboard
3. Fetch logs relevant to the specific invocation that is selected

The way the filtering feature is built is it seems to leverage the exact field name from the source chart that is being used as a filter. In the case of AwsLambdaInvocation, this is named aws.requestId. With current behavior, this will effectively filter out all logs, since this field is not populated in the Log entity.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ umaannamalai
❌ djetter-py

---

djetter-py seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[nashahzad]

lgtm