fix(logger): add setLevel function to set level programmatically

[leandrodamascena]

Issue number: #2303

Summary

Changes

When changing the logging level of a Logger via code, the logging level must be changed. With the current implementation, this was not happening because it was modifying the superclass and not the Logger instance. This PR aims to fix that.

User experience

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

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.

[heitorlessa]

one tiny change and LGTM. Also a reminder for us that this is a workaround until we have a way to fix proxy object (__getattribute__ and __getattr__) while keeping mypy detecting non-existent attrs.

[codecov-commenter]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (653db45) 97.46% compared to head (2d4e6f4) 97.47%.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #2320   +/-   ##
========================================
  Coverage    97.46%   97.47%           
========================================
  Files          149      150    +1     
  Lines         6901     6925   +24     
  Branches       509      509           
========================================
+ Hits          6726     6750   +24     
  Misses         137      137           
  Partials        38       38           

Impacted Files	Coverage Δ
aws_lambda_powertools/logging/logger.py	99.42% <100.00%> (+0.01%)	⬆️

... and 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[heitorlessa]

NOTE for future when we do this properly...

• Remove subclassing from logging.Logger) and subclass from object instead - already commented on why
• Override __getattribute__ to proxy to self._logger -- had to remove it before, and add __getattr__ under TYPE_CHECKING due to Mypy not detecting non-existent attributes

Then we can remove these ugly workarounds, including things like .log_level and anything else that goes straight to the underlying logger

    def __getattribute__(self, item):
        try:
            # Return actual item from our class first (e.g., append_keys, etc.)
            return object.__getattribute__(self, item)
        except AttributeError:
            # Return actual item from the underlying logger (e.g., setLevel, addHandler, etc.)
            return self._logger.__getattribute__(item)