chore(deps): bump rimraf from 2.6.2 to 5.0.10

[mrkans]

Description

Fixes #355

Motivation and Context

How Has This Been Tested?

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• 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.
• My changes are in sync with the code style of this project.
• There aren't any other open Pull Requests for the same issue/update.
• These changes should be applied to a maintenance branch.
• I have added the Apache 2.0 license header to any new files created.

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

[CLAassistant]

All committers have signed the CLA.

[benmccann]

thanks!

@Matthew-Mallimo do you think you could take another look at this? It would fix a number of deprecation warnings that are currently being printed by the library

Happy Thanksgiving!

[code-forger]

@mrkans Thanks for your contribution. It looks like #360 does the same as what this PR does, but includes many other dep updates too.

I will close this PR, however if you think this PR does something that #360 does not, please re-open it.

[mrkans]

@code-forger My opinion is that this one is ready to be merged while that one is not. That PR does the same (and more) but I see no problems in taking this first since it removes a dependency with a known memory leak.

[code-forger]

@mrkans This one is as un-mergable as #360 (conflicting package-lock.json). But, if you can clear your conflicts first, we will merge yours.

[mrkans]

Merge conflict fixed