Draft: add tools to wait for a module to be published on PyPI
Once in a while, some module doesn't actually get updated because PyPI hasn't really refreshed. Hooking this command up to the pipeline will likely help.
We should also have the build-docker-image job double-check that the frozen requirements file really matches the new module version. Maybe we should have a two step process:
- keep the current unprocessed, versionless requirements.txt (committed manually)
- process this requirements.txt to pin the latest versions of swh modules, without dependencies (outside of the container, with PyPI api calls)
- build the requirements-frozen.txt inside the venv, with the assurance that our modules are at the adequate version.