Feature request: feature parity with Python Powertools logger

[saragerion]

Description of the feature request

As addressed in this comment, we should revisit the current features of the Logger to make sure there is feature parity.

Some of the mentioned items are not listed as they are captured by another ticket.

• Logging incoming event functionality
• Custom keys are persisted across warm invocations
• location key in log structure
• Removing log keys (feat(logger): add removeKeys functionality #901)
• Clearing all state (feat(logger): add clear state functionality #902)
• Concept of logger name
• Correlation ID will be captured in Feature request: correlation ID's propagation #129 Feature request: main implementation, randomization, middy middleware, correlation ID's, optional: object merging #139

Problem statement

The Logger utility has a number of functionalities shipped in 2021 that are currently not in TS.

Summary of the feature

For each functionality above:

• Evaluate if the feature should be ported (does it make sense for the TS ecosystem?) or can't be ported because of language's different behaviour

If it can and should be ported:

• Business logic
• Unit tests
• E2E tests
• Examples
• JsDocs (when applicable)
• Documentation

For this reason it's recommended that whoever picks this issue should create one separated PR for each checklist item.

Code examples

N/A

Benefits for you and the wider AWS community

Feature parity with the Python Powertool.

Describe alternatives you've considered

N/A

Additional context

N/A

Related issues, RFCs

N/A