feat(tracer): close & restore segments when other middlewares return

[dreamorosi]

Description of your changes

This PR introduces new logic to the captureLambdaHandler() Middy middleware offered by Tracer to allow it to close and restore any open segments whenever another middleware down in the stack returns early.

This is made possible by the cleanupMiddlewares function shipped in commons in the previous release. The new logic sets a reference to a cleanup function in the Middy internal storage using a scoped key. This way, Middy middlewares that want to return early can call the cleanupMiddlewares function which will execute all the cleanup functions available. This is useful for those middlewares like Idempotency, that want to return a result bypassing the Lambda handler and the normal Middy request lifecycle.

I have also added a unit test case to verify that the cleanup logic is executed.

Related issues, RFCs

Issue number: closes #1536

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]

Successful integration tests run: https://github.com/aws-powertools/powertools-lambda-typescript/actions/runs/5346244981