Until I add Terraform to the image or something.

The linter can't handle it without a project, but it requires setting a
token and I'm fed up with it. If it's not useful as a git hook before
pushing, there's no point in running it in the CI (the CI wouldn't work
if the file is invalid).

Notify me on failure.

It's done with the pull job and it makes the run job faster.

The end goal is pulling and building in parallel and then deployment is
shorter.

This reverts commit d148398f.

"-parallel option is deprecated and will be removed in future versions."

Specifically for GitLab, which takes a long time not only to start but
finish its setup process and until it does it returns a 502. Eventually
it does finish and is healthy but the job already failed.

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.