Maintenance: fix assertions in logger tests

[dreamorosi]

Summary

Vitest has made an update that changes the way tests are spawn (#4011), this causes the path within error stack traces to have changed, making our tests fail.

We should fix these assertions to account for this.

Why is this needed?

So we can safely update Vitest while maintaining test coverage.

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.

[github-actions]

⚠️ COMMENT VISIBILITY 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 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.