Maintenance: write end-to-end tests for the utility

[dreamorosi]

Description of the feature request

### Tasks
- [ ] #1240
- [ ] #1241
- [ ] #1242
- [ ] #1243

Problem statement
Before a Powertools utility can be considered production ready it needs to have e2e tests implemented and running every time a new feature or release is added.

Summary of the feature
This action item tracks the activities and changes needed to integrate the new utility in the e2e tests, which high level and at the time of writing consist of:

• Write the unit tests cases and corresponding functions
• Optionally implement any helper needed
• Add the new utility in the workflow that runs the tests

Code examples
N/A

Benefits for you and the wider AWS community
Confidence that the utility has been tested in a real AWS Lambda execution environment.

Describe alternatives you've considered
N/A

Additional context
All utilities have extensive end to end test cases that aim at testing the different features and usages in a real AWS environment with real resources, permissions, and runtimes.

Related issues, RFCs

#846

[dreamorosi]

Once the linked issues are complete, modify the package.json of the utility so that the test:e2e script starts the tests.

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