Update Sigil process

[TobiasNx]

We are using an old dump from 2013. This makes the transformation pretty pretty slow, since it harvests all updates since then via OAI-PMH.
We have a new one bit it is binary pica+. We need to remodel it.

• Change the process. 462 sigel process new #472
• Add cron job that looks for new updated batch file. That downloads the file to app/transformation/input, renames the file to sigel.dat and cjanges the date in transformation.updates.start="2023-06-01" to the creation date of the sourcefile in conf/application.conf

[TobiasNx]

Deployed with: #450

[TobiasNx]

Reopen this ticket:

Since the process has still some old part and is complicated to comprehend:
Question, do we still need the intervals for OAI, I suggest not, since we only fetch data for a year or so.
We should simplify the process.

Do we need the OAI PMH Data as XML saved at the server?
Do we need this XML Data as fallback?

Tried to simplify the process here:
#489

[fsteeg]

Do we need the OAI PMH Data as XML saved at the server?
Do we need this XML Data as fallback?

If I remember correctly I added this because it was useful to (re-)run the transformation only (e.g. after making some changes), without having to get the data via OAI-PMH again.