Pre-release job should not run when pre-release PR gets merged

[tidoust]

Pre-release workflow runs on pushes. The workflow ran as a result when #217 got merged.

Release job did not run (see #222), but even if it had, chances are that the new CSS package would not have been already released by the time the pre-release workflow runs.

Pre-release workflow should probably rather only run after the update-ed workflow has run (see #219) to avoid running in such situations.

[tidoust]

Pre-release workflows updated to run after the update-ed workflow.

Workflows still run on pushes to the default branch to detect manual changes, but won't react on version bumps to package.json files. That is not perfect: if an admin decides to release a minor version of a package, they will bump the version in packages/xxx/package.json accordingly and that change won't be picked up automatically. In other words, the admin will have to run the pre-release workflow manually after the bump, or wait until the workflow runs by itself (after next crawl).

Ideally, the workflow would also run when changes to package.json files are pushed to the default branch, except when these changes are the result of merging the pre-release PR. That requires mapping the push event to the PR somehow. Leaving this issue open to figure out how to do that.

[tidoust]

I created #226 to track remaining work and will close this after all. The bug itself was fixed. What remains is more something to improve than a bug.