Handle situations where case registration fails

[perolavsvendsen]

HOOK workflow "create_case_metadata" creates case metadata AND registers the case on Sumo (if enabled).
In the cases where Sumo is down, or connection for other reasons fail, case metadata will still be made, but case will not be registered on Sumo. FMU workflow will continue nevertheless.

• Case registration should not wait for a 504 timeout. In the cases where Sumo does not respond, it should make a few attempts, but not wait for a long time. Fail faster.
• In the situations where case has failed to be registered, the SUMO_UPLOAD jobs should immediately quit. (e.g. if case is not found on Sumo, then move on immediately.) (e.g. replace current OSError with a userwarning, and move this check to the top of the script so that it runs before adding all the files.)