Maintenance: Fix `TracingE2E` test to avoid occasional timeouts

[phipag]

Summary

In the v2 branch GitHub workflows we see regular timeouts caused by the TracingE2E test retrying longer that the STS role expiration date. It seems that sometimes the traces generated by the E2E test cannot be retrieved.

Example of failing test: https://github.com/aws-powertools/powertools-lambda-java/actions/runs/15049118451/attempts/1

Why is this needed?

This is needed to achieve reliable E2E tests e.g. during release workflows.

Which area does this relate to?

No response

Solution

There might be a problem in the TraceFetcher: https://github.com/aws-powertools/powertools-lambda-java/blob/v2/powertools-e2e-tests/src/test/java/software/amazon/lambda/powertools/testutils/tracing/TraceFetcher.java

The retry strategy is also too long.

Acknowledgment

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

[phipag]

Created PR #1847 to disable the offending test temporarily.