refactor(utils)!: make snark-artifacts utility functions dynamic

[cedoor]

Description

This PR is a first step to make the utility functions to get snark artifacts more dynamic, i.e. less independent from changes in the snark-artifacts repository. As mentioned in this PR's comments the code related to these functions will be moved to another package in the snark-artifacts repo. Further checks on parameters could be added in the next step.

Comments have not been added as this code will be moved to another package as mentioned above.

Related Issue(s)

Closes #272

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have run yarn style without getting any errors
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[cedoor]

@sripwoud I have deliberately over-minimized those functions ta make them simpler and project-agnostic, but it makes sense to re-integrate parts of your code now. Let's discuss them!