Maintenance: upgrade vitest to next major

[dreamorosi]

Summary

Vitest released a new major version (4.x) and introduced some breaking changes around code coverage in the process.

These changes make our CI fail as shown in #4679. We should fix this.

Why is this needed?

So that the same coverage is maintained and tests continue to pass.

Which area does this relate to?

No response

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.

[powertools-for-aws-oss-automation]

Warning

This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing 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 v2.29.0 version!