feat(commons): add cleanupPowertools function

[dreamorosi]

Description of your changes

This PR introduces a new function used to cleanup Powertools for AWS resources when a Middy middleware returns early and terminates the middleware chain.

When a middleware returns early, all the middleware lifecycle functions that come after it are not executed. This means that if a middleware was relying on certain logic to be run during the after or onError lifecycle functions, that logic will not be executed.

All Powertools for AWS middlewares rely on these lifecycle functions to perform some operations like:

• close and restore the segments for Tracer
• flush stored metrics for Metrics
• clear any existing state in Logger

The function in this PR is aimed at advanced Middy users who author their own middlewares, as well as ourselves in future middleware implementations. The idea is that when writing a middleware that might return early you only have to import the cleanupPowertools function and run it before returning early. The function will then take care of inspecting the Middy internal object and execute any Powertools related function that might be present.

Related issues, RFCs

Issue number: #1410

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my change is effective and works
• The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

---

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.

[dreamorosi]

@am29d renamed the function as discussed, ready to review!