Haha, I understand that much myself. For internal reasons, I have been instructed to do it this way, though I am completely aware of and familiar with the things LAVA has in place to achieve the same tasks.
The job as written there is to download a set of framework scripts, so that depending on the tests variable and options provided in the final command, it does different things. In that version it will simply do smoke tests, but it could also be given options telling it to download some file(s), which can be quite large depending on the purpose. Ideally the download of those files can be handled by the script(s) so that they can end up directly on the DUT and to simplify the information needed of test writers (just a version name instead of a whole path), but where it isn't possible we'll just have to settle.
Best regards, Michael