The job is now hidden, so you can base on it and set a proper script to
run the CLI.

When building ci-images, images on the host are sometimes (in the case
of the docker image, always) pulled from the registry (overwriting the
tag) but before pushing. So the image pushed is that pulled just now.
Instead save the build hash (and pretty much everthing else) and re-tag
before pushing (using the hash so it's the right image). While at it,
unify the Docker push jobs (the Docker Hub and the personal registry
one).

Faster and no rate limits. Win-win.

Jobs for building and pushing to the Shore Docker image registry as well
as Docker Hub.

Useful for pre-commit hooks repos.

- Don't include templates in templates.
  I now think that it can cause issues later on.

- ci-fairy complains if a job needs a missing jobs, but with hidden/
  templated jobs it doesn't work as expectee.

- Rename the PyPI upload template.
- Add wheel build and test install jobs.

- Merge the Docker CLI and Docker Compose templates.

An optional job to push to Docker Hub. Copied from the Docker Hub
template.

Build and push an image to Docker Hub. Match the image tag to the
branch.

Include in the templates. Also, for Docker deployments, run the tests
(pre-commit) first and then build the images.

Run almost everything in ns4 (it's the fastest and least used). Don't
set the runner for Docker deployments, allow the project to set the
default.

This reverts commit 5b3aeb85.

Didn't work as expected.

Instead of having just hidden jobs and extending it in the project, use
a variable that can be overriden in the project (not sure it will work).

For real this time.

Don't create new ones in templates.

- ci-fairy pre-commit check.
- Correctly show failing ci-fairy test.

Copied from existing projects.

- bats
- pypi upload
- docker-compose build and run
- gitlab release
- build presentations

Also, some pre-commit checks and a CI for it.