Maintenance: improve e2e assertions on traces & idempotency

[dreamorosi]

Summary

Following some changes on AWS Lambda side, we need to improve our integration tests around Idempotency and Tracer so that they correctly assert the shape of traces and logs under certain conditions.

Why is this needed?

So that we can continue running integration tests on our cade and keep the confidence in our codebase at a reasonable level.

Which area does this relate to?

Tests

Solution

No response

Acknowledgment

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

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[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.