Update Node version in release workflow

[dhruvmanila]

Summary

This PR updates the minimum Node version to 22 and is a follow-up from #631. The dependencies that we use to publish the build artifacts bumped the minimum version of Node to 20. I've bumped it to 22 as that's the minimum active LTS version right now.

Along with the node version bump, this PR also updates the said dependencies (ovsx and vsce) to the latest version which requires a minimum node version of 20.

Test Plan

When I perform the next release :)

[MichaReiser]

We could consider testing this together with upgrading the release dependencies

[dhruvmanila]

We could consider testing this together with upgrading the release dependencies

Yeah, makes sense.

[MichaReiser]

Note. I think the marketplace have a --dry-run flag or similar that we could use to test the change without publishing.

[dhruvmanila]

Note. I think the marketplace have a --dry-run flag or similar that we could use to test the change without publishing.

Hmm, I don't see a --dry-run or related flag in the vsce / ovsx tools that we use to publish.

[MichaReiser]

I guess you could try --skip-duplicate but feels risky. I'm also up to just merge and revert if we run into problems during the next release.

[dhruvmanila]

I guess you could try --skip-duplicate but feels risky. I'm also up to just merge and revert if we run into problems during the next release.

Yeah, that does seem risky. Another option would be to create a dummy account and do the release there but I think I'd just prefer to merge it and make a mental note to verify when doing the release.