Add support for Argo artifacts about hera

[flaviuvadan]

@tachyus-ryan I started working on this today and I think I have a path forward. I am currently trying to determine how to best abstract away the GCS/S3/HTTP/etc. specifications from the artifacts so users focus only on the task artifact input, task artifact output, etc. Specifying those is also interesting because of the intersection between the two concepts (I/O artifact), with the main difference being that the input artifact requires a task name. I will report back when I have a PR; will also tag you in it.

[flaviuvadan]

This would be a great addition, for the reasons you mentioned! I will look through what this might require and come back with some suggestions we may discuss.

[tachyus-ryan]

In thinking through this a bit more, sharing a volume seems like it might be just as good or possibly better for most use cases. I'll try to think of reasons why artifacts might be a better option. I think input artifacts might be the most reasonable as they would allow you to retrieve data sets without having to first load them explicitly in Python. Output artifacts would serve a nice way to store data sets without doing so explicitly. However, artifacts within a workflow specified in Hera seems like it might be unnecessary.

[tachyus-ryan]

@flaviuvadan thank you very much!

[flaviuvadan]

Just posted #27. Apologies for taking way longer than expected... 🙁 will try to get features out in a more timely fashion going forward.