Maintenance: V2 updates - review interface & propose improvements for Tracing module

[scottgerring]

Summary

We should use the V2 release as an opportunity to reflect upon the interfaces of our existing modules and identify areas of improvement. This work has been done as part of rewrites for some modules, and in isolation for others - check out #1283 for details.

Why is this needed?

• Minimize the likelihood that we need to make more breaking changes to PT-Java again soon in the future
• Double-down on the quality of the project by forcing large-scale code review
• Increase knowledge of the modules around the contributor team

Which area does this relate to?

No response

Solution

1. A review of the current module, its public interface and structure, and potential areas for improvement documented on this ticket for discussion
2. A draft PR against the v2 branch showing the high level impact of proposed changes
3. PR completed and merged into v2

Acknowledgment

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

[AlexeySoshin]

Happy to take a look at this!

[scottgerring]

@heitorlessa - what do you think about this - do you have a view on whether or not all languages should be going modular with regards to the tracing providers like python has?

[scottgerring]

I noticed that the way we are including tracing at the moment pulls in bits of the V1 AWS SDK. We should definitely fix that while we are here.