fix(launcher-api): remove orphan JobResults visibility permissions

[mabw-rte]

Context:
In the job listing of AntaREST, we call two endpoints:

• GET, v1/launcher/jobs
• GET, v1/launcher/jobs/{job_id}/progress
  It turns out that when user does not have a permission for some job, this job, though listed (using the first endpoint of jobs), spits out an error 403 when it is called for the second endpoint progress.

Issue:
For the endpoint jobs, the logic beyond the permissions includes a second option where when an orphan job is created recently enough would become visible to everyone. This logic was not included in the progress endpoint which leads to the Exception above.

Solution:
After consulting the application users, they think that this orphan visibility logic is not that much relevant and should be removed (at least temporarily).

[MartinBelthle]

Seems good to me just a minor change

[MartinBelthle]

You can also remove the import of timedelta that we don't use anymore I believe

[mabw-rte]

@sylvlecl, il faudrait priviligier de rebase en local ... Tu pourrais voir avec @skamril, on a deja eu la discussion