Tech debt: Improve Metrics provider to make it more maintainable

[leandrodamascena]

Why is this needed?

In the PR #2194 we refactored the Metrics utility to allow bring new utilities. But it created some technical debt that must be addressed now.

Some items we need to fix:

• Cleanup the slight confusion in OOO / Protocol
• Fix possible mistakes in docstrings
• Remove old and commented code
• Refactor extract* into standalone functions to reduce call graph
• Split up functional and unit tests with new providers

Which area does this relate to?

Metrics

Suggestion

No response

Acknowledgment

• This request meets Powertools for AWS Lambda (Python) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

[heitorlessa]

adjusting labels to prevent incorrect metrics

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under 2.23.0 version!