We changed the Jenkins configuration to pull from GitLab while the mirroring to
Gitolite was not working:

  tails/jenkins-jobs@4db52b22

But we did not adjust this post-receive hook accordingly,
so the "pushing to Git triggers a Jenkins build" behavior
is broken.

Let's repair this, until we make up our mind (tails/sysadmin#17715)
wrt. whether we should keep pointing Jenkins to GitLab's tails/tails,
or use the local mirror we have on puppet-git.lizard.

This reverts commit 8f58ff06.

Without disabling CSRF (complicated, will probably become impossible at some
point), we did not manage to have jenkins-job-builder use the API
with current Jenkins LTS. Using the standard security setup
(https://wiki.jenkins.io/display/JENKINS/Standard+Security+Setup),
an actual user, and its API token, repairs communication with the API.

refs tails/sysadmin#16955

refs: tails/sysadmin#16955

Closes tails/tails#17755, tails/puppet-tails!7

Now that we're running check-mirrors.rb 4 times more often,
there's greater chances that 2 of them end up running at the same time.
Let's avoid having to reason about how check-mirrors.rb manages
shared resources such as its failures.json state file.

refs: tails/tails#17755

refs: tails/tails#17755

refs: tails/tails#17755

See: https://salsa.debian.org/tails-team/gitlab-migration/-/issues/55

I'll change manually in repo during deploy.

See: https://salsa.debian.org/tails-team/gitlab-migration/-/issues/74

I'll modify manually in the server.

For some reason, our script is not detecting some dependency constraints
correctly, so i'm pinning this one manually.

From: https://github.com/django-compressor/django-compressor/blob/2.4/setup.py#L148

It is now installed with pip. I'll remove the package manually from the
server after deploy.

It was missing a change of directory, bug was introduced in:
9a166c00

refs: tails/sysadmin#17719

We need to account for longer version strings than the one provided by
the Pypi JSON for some packages.

In the case at hand, Pypi will return "2.1" for latest user-agents
version, but we should be looking for "2.1.0" in GitHub tags.

The version in the Pypi JSON is "2.1" but there's no such tag in the
repo and our dep update script does not currently account for such
differences.