Maintenance: move e2e utilities into testing package

[dreamorosi]

Summary

In a recent PR we have created a new internal package dedicated to include all the utilities that we use for testing the project. Some of the helpers, namely the ones to create a Lambda function with CDK, invoke it, and collet its log were left out of that PR.

We should move these helper from their current location into the testing package.

Why is this needed?

This action is needed so that . This will prepare the codebase for #617 which is a prerequisite for #1375.

Which area does this relate to?

Other

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.