You can now more easily run the update script to finish out an update
and the documentation is updated to match.

For some reason, I never actually published the draft on this one.
Since 4.121.0 will be out shortly, opted to just skip it.

I think the syntax changed when we moved from yarn to npm.

The -dev seems a bit weird since it is not a dev version once it is
built, and also there is a false positive advisory with the code-oss-dev
name.

There is a new use of parsedArgs so we have to pass that in since we
parse on demand instead of globally.

Providing our own type is trivial.

It needs to parse the version *after* the VS Code update, otherwise it
is just pulling whatever the previous version was.

That means we cannot use it in the step title without some refactoring;
opted to just omit it for now.

The problem was that whenever the hashe needed an update, the current
patch would create a conflict which cannot be easily auto-resolved.

Instead, put the hashes in a separate patch that is deleted and
regenerated each time, avoiding the conflicts.

Also the web worker iframe hash was not being updated.