feat(ci): Link all versions during release

[phated]

This PR upgrades the release-please tool we use to v13 (v3.x of the action), which requires us to switch up the uploader actions to the one I built for libbinaryen and binaryen.ml.

The upgrade was primarily to switch from the node-workspace plugin to the linked-versions plugin so the version of every package is exactly the same. We still need to update the versions inside our @grain/cli dependencies, so I'm using the extra-files feature of release-please to update those versions, which means we no longer use a caret on those versions.

I encountered various problems when updating all of this:

1. npm v7+ broke their filename property in npm pack output: [BUG] npm pack incorrect filename for scoped package npm/cli#3405
2. release-please doesn't work with some combination of grouped-pull-request-title, linked-versions and node-workspace: group-pull-request-title-pattern doesn't work with linked-versions plugin googleapis/release-please#1456
3. release-please doesn't work with both linked-versions and node-workspace, requiring us to use extra-files: linked-versions and node-workspace plugins are incompatible  googleapis/release-please#1457

You can see an example of the "linked-versions" PR at phated#2 (notice the various "Synchronize Grain versions" changelog entries).

And you can see an example of a full release at https://github.com/phated/grain/actions/runs/2411992148 (the docker dispatch failed because I disabled the docker workflow in my branch)

[ospencer]

Absolutely amazing work!

[marcusroberts]

Great deep dive to fix all these issues!