Handle failed runs due to identity checks better

[haydentherapper]

Description

Currently, if the run fails because identity checks fail, we show the job as not succeeded, which means that the checkpoint that was successfully verified will not be written to the GitHub Action as an artifact. This means that the next time the job executes, it will have to run through twice as many entries during an identity check. Additionally, a failed identity check is likely a bug in the monitor.

I would recommend that we:

• File an issue in the repo where the action is running for the entry that had an issue
• Skip that entry and continue so that the job will succeed

[haydentherapper]

This one came up again, when an entry had an incorrectly encoded extension in a certificate. We really need to fix this because it makes catching up exponentially harder with each failed run.