Maintenance: bump dependencies & drop Node.js 14 on v2 branch

[dreamorosi]

Summary

While we will be discontinuing Node.js 14 support on the mainline according to the plans described in #1664, we can already do so in the long running feat/v2 branch.

Why is this needed?

Doing so will allow us to bump a number of dependencies that we were holding back (i.e. lerna, eslint, etc.) on as well as focusing on improving the utilities without having to worry about compatibility with a runtime that we will have dropped by the time v2 comes out.

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.

[github-actions]

This is now released under v1.14.0 version!