rsync can fail with zero exit code: impacts bulk_move_job_rsync

[pansapiens]

If rsync fails with the error ssh: Could not resolve hostname example.com: Temporary failure in name resolution rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: unexplained error (code 255) at io.c(235) [Receiver=3.1.3]' it returns a zero exit code.

The task laxy_backend.tasks.job.bulk_move_job_rsync will appear complete when it in fact failed in this instance. We need to parse this error and treat it as a failure.

[pansapiens]

Also, when archive path is not writable, this returns without raising an error in bulk_move_job_rsync:

mkdir "/some_job_id" failed: Permission denied (13) *** Skipping any contents from this failed directory *** some_job_id/ 

rsync error: some files/attrs were not transferred (see previous errors) (code 23)