As recommended by 'npm pkg fix'.

* Verify release commit is in the main branch

Typically the tag is pushed first, CI runs, clearing the way for 'main' to be pushed. However we must not release until this is done.

* Improve CI status check

Execute logic within jq; look for any passing workflow and fail if there are none.

* Execute package.json check within jq

No need for Bash, jq can handle this.

* Perform package.json check first

It's the most important check, are we publishing what we think we're publishing.

* Update instructions

This change ensures that all messages from the worker are received by
the main process before the worker exits.

It solves issues on Windows that are occurring with Node.js v20 and later
when `workerThreads: false` is set in the AVA configuration.

Fixes: #3390

* Update comment and rename message

Whether the worker exits depends on whether user code is keeping the event loop busy. 'Freed' is a better term.

---------

Co-authored-by: Mark Wubben <mark@novemberborn.net>

Rulesets prohibit pushing commits on `main` without a PR. This means that running `npm version` within `main` actually
creates more work. Further, the release workflow requires CI to have passed on the tagged commit, but it's triggered
when the tag is pushed.

Simplify by triggering on pushes to `main`, when that commit has a release tag. We can then create a PR for a release
branch, push the tag commit, and trigger the release when merging the commit into `main`. This still has to happen
locally since we must include the tagged commit.

* Update dev dependencies

* Update dependencies

* Rebuild lockfile