feat(logger): implement addFilter/removeFilter to address static typing errors

[heitorlessa]

Issue number: #3358

Summary

Adds addFilter method that was previously missing so static type checkers are happy.

NOTE: By default, Logger proxies any missing public method or attribute to its private logger (_logger) to avoid any runtime issues, so this wasn't an issue at runtime.

Changes

Please provide a summary of what's being changed

• Add addFilter public method
• Add removeFilter public method

Unrelated changes

• Add logging._ExcInfoType in exception() method as per Static typing: Logger.exception() exc_info type does not match Python's built-in one #3356

User experience

Please share what the user experience looks like before and after this change

Experience in adding a filter like it was before but without any mypy errors

import logging
from aws_lambda_powertools.logging import Logger
import secrets

logger = Logger()


class ApiKeyFilter(logging.Filter):
    def filter(self, record):
        if getattr(record, "api_key", None):
            record.api_key = "REDACTED"

        return True


logger.addFilter(ApiKeyFilter())

logger.info("Blah", api_key=secrets.token_urlsafe())

JSON output

{
    "level": "INFO",
    "location": "<module>:18",
    "message": "Blah",
    "timestamp": "2023-11-21 09:59:48,477+0100",
    "service": "service_undefined",
    "api_key": "REDACTED"
}

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (060ce36) 95.39% compared to head (59e3d72) 95.37%.
Report is 1 commits behind head on develop.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #3380      +/-   ##
===========================================
- Coverage    95.39%   95.37%   -0.02%     
===========================================
  Files          208      208              
  Lines         9633     9637       +4     
  Branches      1766      805     -961     
===========================================
+ Hits          9189     9191       +2     
- Misses         330      331       +1     
- Partials       114      115       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

No Coverage information
3.3% Duplication

[heitorlessa]

@sthulb good to go now, ignored Sonar rule in functional test as it doesn't pose any risk (we want to redact sensitive data in our test).

One last CI check (Python 3.11) and passing that it's good to merge. tks