Maintenance: add Idempotency utility to unit tests

[dreamorosi]

Summary

Given that #1110 is now merged it's now a good time to add the new utility to the unit testing ran at different points of the dev lifecycle.

Additionally, there were some inconsistencies in the package.lock dependencies that prevented some other CI processes from completing successfully (example of failed run).

Why is this needed?

To increase confidence in the code to be merged and to prevent regressions.

Which area does this relate to?

Tests, Idempotency

Solution

See linked PR

Acknowledgment

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

[dreamorosi]

Closing this in favor of #1100

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