Currently, `curl` exits with a 0 status code for HTTP/301, which is
the case for both existent and non-existent artifacts in nexus3,
breaking the logic behind duplicate artifact checking.
This should fix uploading aarch64 artifacts, which are currently
wrongly detected as duplicates due to the above quirk.
Change-Id: I6b3164476b4fcb95115934eda72d53edf102858b
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>