This was missed in earlier checks because nothing is really using these
two images. I did consider removing them completely as a result, but
having them run tests (and fail) was a good sanity check that what we
are doing generally works if set up correctly. These images were not set
up correctly so failed.
We want to move our base python images to quay.io and then pull those
images from there when building gitea-init and jinja-init images. To do
that we need to use the container build job set and not the docker build
job set. So switch both images over and in the process publish the
images to quay.io. Then we can can also consume the base images from
quay.io as well.
We switch to building with docker now that docker is capable of
building with speculative images in single arch builds.
Change-Id: Ic4cda82a80806112995ae77a49bf5c7be6654ec6
f1649fd7e6