Also run the `rust` checks on "milestone" CLI releases, to ensure we
remain backward compatible with those versions. This was prompted by
https://github.com/github/codeql-action/pull/2960#pullrequestreview-3104730221
Running this on current `main` and then on that PR should improve our
confidence we remain backward compatible.
It also turns out a probable `ruamel.yaml` update was changing a lot of
generated workflows, so I've:
* fixed the `ruamel.yaml` version to the latest in `sync.sh`
* added `yaml.width = 120` in `sync.py` to minimize (but not entirely
remove) the number of changes
* checked in the workflows whose formatting was changed by the new
`ruamel.yaml` version
Both the justfile and the pre-commit configuration for the `pr-check`
sync were broken:
* justfiles run recipes one line at a time in a fresh shell, so the venv
activation was not working
* the pre-commit config was relying on an installed `ruamel.yaml`
pakcage, but the default one installable via `apt` on Ubuntu 24.04 is
old and generates different output (with formatting differences).
Now:
* the venv dance is put in a separate bash script
* both just and pre-commit will use that same script, so both problems
will be fixed
As a bonus, a root `justfile` is added exposing the `update-pr-checks`
recipes plus a `build` one. Running `just` without arguments will also
now call the default `sync` recipes that will call both of the above.
