Artifact download and upload path syntax differs from unix tools like cp and mv

Double check the behaviour of the artifact downloading gear:


And make sure it's consistent with the rest of the unix world with how tools like `cp` work

Start by reproducing the artifact download and upload path behavior described in the issue, then compare it with the operand syntax used by Unix tools such as cp and mv. Done means both artifact operations follow the expected Unix-style path conventions.

Written by the indexing model from the issue text.