Automated circuit artifact upload for release workflows

[wwared]

When running the full end-to-end groth16 flow, it looks like the default pre-built upstream SP1 circuit artifacts are no longer enough for verifying our proofs (verified with an aptos LC proof).

Either way, we may want to define a place to host these artifacts once we perform stable releases and make sure that we're using our own circuit artifacts by default instead of upstream's.

[wwared]

Once plonk is merged into dev, we will have:

• A public S3 bucket with the circuit artifacts
• Code for downloading the right artifacts when generating a proof

Now we only need:

• CI workflow for publishing the artifacts to S3 when we make a new release
• CI automation that lets us know when a PR requires re-generating the published artifacts (There is now a test_e2e_check_parameters test that attempts to check this flow, see chore: E2E test for checking if Plonk parameters require regenerating #69)