Update checkpointing in alpine and maven pipelines

When running the alpine and maven pipelines to collect package urls, both actions time out after 6 hours. We should have a way to keep track of where we are when we are processing an index file so when we are interrupted, we can start off where we were.

For maven, the order of packages in the index is deterministic for a given version of the index, when the index is updated, the order of packages is not always the same as the order it was in the previous index.

We would need to keep track of the index file checksum to see if we can resume from the index file or if we have to start over because the index is different. We would also need to track which package we last processed so we know where to pick up from.

Start by locating the alpine and maven pipeline entry points and the code that processes each index file. Check how the current index checksum and last processed package could be stored and restored. Done means an interrupted run resumes when the checksum matches and starts over when the index changes, for both pipelines.

Vom Indexierungsmodell aus dem Issue-Text verfasst.