Maintenance: move away from `lerna version` command

[dreamorosi]

Summary

As part of the migration off lerna we should remove our usage of lerna version and bump our project's version + generate the CHANGELOG in other ways.

Ideally whatever we'll end up using should live as an action under aws-powertools/actions so that it can be reused by aws-powertools/powertools-mcp and other Node.js-based repositories under this org.

Why is this needed?

See reasoning in the parent issue, but ultimately removing it would allow us to do this:

 npm un lerna

removed 554 packages, changed 2 packages, and audited 1088 packages in 5s

found 0 vulnerabilities

Which area does this relate to?

Automation

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.