Feature/175/lambda request id in logs minimal

[pjhartzell]

Related Issue(s):

• Logs need to include lambda request ID, if applicable #175

Proposed Changes:

1. The self.logger creation in the Task initializer now picks up the aws_request_id kwarg and combines it with the payload id to generate the prefix for log messages.
2. The logging message format is augmented with the AWS lambda Request ID, if it is passed:
   • It used to be [<payload-id>] <message>, which produced logging output like INFO:logger-name:[payload-id] Some message.
   • It can now be [<payload-id> <lambda-request-id] <message>, which produces logging output like INFO:logger-name:[payload-id lambda-request-id] Some message.
3. The docs example now shows how to pass a Lambda request ID to the handler when building a stac-task for a Lambda.

Note: This is intentionally minimal. A deeper look at how stac-task handles logging is in progress.

PR Checklist:

• I have added my changes to the CHANGELOG or a CHANGELOG entry is not required.