Index Alma data triggered by webhook: daily updates and basedump

[dr0i]

Complements #1112 .
Fundamental to solve #1162.

@blackwinter has implemented a webhook which would call a (to be implemented) webhook listener to inform it about when the updates/basedump files are ready.

• implement a webhook listener
• index the data when webhook listener gets triggered
• put webhook listener into monit to ensure its living (as it is part of lobid's web app it is already monitored)
• get SSL certificate
• restrict to SSL
• configure webhook listener in the webhook

Deletions are atm not important but would complement this issue.

[blackwinter]

There are two possible webhooks (per type of run):

1. baseline: Gets triggered when a baseline run finishes.
2. update: Gets triggered when an update run finishes.

Both URLs may contain the following optional placeholders:

• %{job}: The job to trigger (in our case: Jenkins job name); configurable per type of run (see above).
• %{token}: A secret to protect the listener from unauthorized access (in our case: Jenkins Authentication Token); configurable per type of run (see above).
• %{cause}: Some metadata pertaining to the run triggering the webhook; dynamic per run.

For Jenkins, our URL would currently look like:

http://JENKINS_HOST/job/%{job}/build?token=%{token}&cause=%{cause}