/reviewed-on nexedi/slapos!540

--force with --check-anomaly makes monitor.runpromise execute the promise
unconditionally, even for testless ones.

Update versions and tweak a bit python language server config.

After some investigation, I understood that completions where slow for us because jedi add some [buildout support](https://github.com/davidhalter/jedi/blob/cef769ecd8b3a50cd0784d8660b123f4bf0eaec2/jedi/evaluate/sys_path.py#L132-L137) which walks up directories to find a `buildout.cfg` and inspects the corresponding scripts in `bin` to find python package paths. On web runner I have 98 scripts in `~/bin/`, each of them adding between 30 and 50 entries to `sys.path`.

A quick workaround is to create an empty `buildout.cfg` in the current directory or a parent directory before editing python code.

/reviewed-on nexedi/slapos!509

/reviewed-on nexedi/slapos!539

Building Bison 3.3.2 now requires autoconf.

fixup for af247599: Put automake
in $PATH instead of creating its own environment variable.

Needed for kedifa!2

/reviewed-on !537

otherwise hdf5.so cannot be found on compilation of h5py

more-itertools is a hidden dependency, not managed by buildout.
It has dropped support for python2 after version 5.0.0

/cc @tomo @jm

/reviewed-on nexedi/slapos!536

This partition contains no data worthy of backup:
- only in-transit emails appear
- logging is (sadly) not local to the partition

- Use `xz-utils` component for log file compression
- Fix some stacks and software releases to use the logrotate stack instead of re-creating it:
  - `software/caddy-frontend`
  - `stack/resilient`

/reviewed-on nexedi/slapos!508

Use xz instead of gzip.
Also put the cron script in etc/service instead of etc/run (to have the
"cron-on-watch" process)

Building Bison 3.3.2 now requires automake.

OpenVPN fails to build on Debian testing because
net-tools is no longer provided by default.

/reviewed-on nexedi/slapos!534