Error in the production and pull-requests workflows

[vplasencia]

Context

https://github.com/privacy-scaling-explorations/zk-kit/actions/runs/8836779105/job/24264124859

https://github.com/privacy-scaling-explorations/zk-kit/actions/runs/8909151442/job/24466017647?pr=279

[sripwoud]

@cedoor and I are aware of this.

See #273 (comment)

The main root cause is that the single CDN we currently use to download the artifacts is throttling downloads. This happens especially when automating downloading artifacts concurrently.
2 already on going actions to solve this:

1. use multiple CDNs and retry fetch mechanism: see feat(utils): use multiple sources to download snark artifacts #273 and refactor(utils)!: make snark-artifacts utility functions dynamic #275 (comment)
2. In the tests for the -proof packages, we should stop testing ALL the parameters cases (e.g poseidon for 2,3...16 inputs). This requires downloading all the artifacts which takes too long. Most importantly testing the correct proof generation for different parameters is in the scope of the circuit package, not the *-proof packages. See refactor(utils)!: make snark-artifacts utility functions dynamic #275 (comment)