ci(release): use trusted publisher, update related deps

[nicklmart]

Description

Prepare a workflow that can be used with npm's new trusted publisher system.

Motivation and Context

This system uses OIDC and is more secure (and requires less maintenance) than generating a 90 day token.

How Has This Been Tested?

CI change, all tests green.

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?

This package will be releasable again!