Allow Post processors to give up on attempts + check on GS processing time on OCR

[DiegoPino]

What?

A few things.

• First I'm not sure if the "timeout" we have set per Processor is being respected. I just saw an OCR being stuck for a day. Code might have changed in PHP 8.1 that requires me to double check if we are enforcing this. I have a test file I can use
• Also, a timed out Processor might re-enqueue itself. Chances are if it failed once, twice, 3 times might not solve the issue. Adding a checkbox that logs the attempt and gives up would be idea
• On Hydroponics. I should be able also to report what is running/how long it has been running and allow an admin to intervene and kill the process (not hydroponics but kill the child process).
• I should also be able to mark further processing of the same ADO (e.g pages of a PDF) fruitless
• Also GS. I have seen on complex (not linearized) PDFs GS failing to export an image from a PDF and ending in a day long loop. Since we have a way of killing OCR (which I always thought was the issue with complex stuff) we should actually look more closely to PDFalto and GS ...and do the same. + Log it. Like LOG it hard

@alliomeria this is re: today's queue issues

[alliomeria]

Giving this a bump @DiegoPino, we saw a related happening today related to a color conversion issue jamming up a queue.

[DiegoPino]

@alliomeria PHP 8.1 is not handling timeouts as it used to in the same way, which means a stuck process is not timing out. I will have to modify the methods we use. Killing is still working. But also our swapping between queues when something fails is leading to CRON taking over long running processes that should only be handled (e.g OCR) by the background. So will open another issue to follow up with this