Maintenance: Fix flaky unit tests when truncating temporary files

[phipag]

Summary

Depending on the (random) order of execution in junit tests truncating files should always assume that the file was not there before and catch NoSuchFileExceptions.

Why is this needed?

To avoid random failures in GitHub worklows.

Which area does this relate to?

Governance

Solution

No response

Acknowledgment

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