Better error message

[k-yle]

Description

Motivation and Context

Fairly straightforward PR. I was struggling to debug an issue because the original error from spawn isn't shown to the user

How Has This Been Tested?

Tested in my code, now you can see the error - which was ENOMEM. Also added better unit tests

Types of Changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Documentation (adding or updating documentation)
• [ ] Dependency update

Checklist:

• [ ] My change requires a change to the documentation and I have updated the documentation accordingly. N/A
• [x] My changes are in sync with the code style of this project.
• [x] There aren't any other open Pull Requests for the same issue/update.
• [x] These changes should be applied to a maintenance branch.
• [ ] I have added the Apache 2.0 license header to any new files created. N/A

What is the Impact to Developers Using Jest-Image-Snapshot?

nicer errors

[CLAassistant]

All committers have signed the CLA.

[oneamexbot]

:tada: This PR is included in version 4.4.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: