feat: enable support for node16

[wdconinc]

This upgrades this action (and actions used in ci) to node16, applies npm audit fixes, and removes all but the unexpected input warnings by switching away from set-output.

New check_dist check is from https://github.com/actions/typescript-action/blob/main/.github/workflows/check-dist.yml, also MIT licensed.

[nickofthyme]

This is great! Thank you so much.

I'll run the checks and merge ASAP.

FYI I'll tag it under v2 to avoid any breaking changes on v1.

[wdconinc]

Tagging as v2 is indeed what I would have done too. I noticed that you tagged v2.0.0 but not the v2 (actions doesn't automatically interpret semantic versioning but requires those tags to be explicitly created, like the v1 tag).

[nickofthyme]

Yeah, back when I started this action GitHub suggested here to use v2 to bind the latest stable major version. This doc also has not been updated in 2 years.

But after looking at a few popular actions, including some from GitHub like octokit/request-action, I noticed they stopped doing the v2 tagging. Maybe they favor using v2.x instead. But I don't see any issues mentioning this naming change.

That said I'm happy to add the v2 tag if you'd like. Let me know.

[wdconinc]

octokit/request-action has a release series branch v2.x instead of an ever-changing tag. I think having a similar approach here would be useful too. It avoids having to use main and potentially ending up with incompatibilities. In any case, it's your call what you wish to do, of course.

[nickofthyme]

Oh I see, I wondered how they resolved the v2.x, the branch makes sense. I'll just add the v2 tag since I don't imagine a ton of future releases. Thanks again!