WebODM fails a task if a connection error happens

[pierotofy]

In some instances, a task might be flagged as "failed" although NodeODM is still processing the task (and returned an error due to a "hiccup").

This should be fixed by making WebODM more fault tolerant (retry).

A user reported the following for the task failure description:

Unauthorized. Do you need to set a token?

Even though NodeODM was still processing.

[askeuhd]

To expand; I filed the report with Piero. The server running WebODM is connected to the internet via a cable ISP that has been known to drop out, which seems like a likely cause of the "hiccup".

[pierotofy]

Also happens if a process "hangs" for longer than the allowed timeout (happens if the OS starts swapping RAM), freezing the computer state for longer than ~30 seconds.