Maintenance: address integration test flakiness

[dreamorosi]

Summary

In #1661 we have made significant changes in the integration test infrastructure, we have however introduced some transient failures due to the naming of some resources.

Before moving onto new areas we should address this.

Why is this needed?

So that the tests can be run consistently.

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 ⚠️

Comments on closed issues 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.