ci: Add release workflow

[samuelburnham]

Adds a release workflow based on argumentcomputer/zk-light-clients#19 and argumentcomputer/aptos-core#5

TODO:

• Do we also want to bump the Cargo.tomls for tests, examples, and cli/src/assets?
• Make an issue to reusify this workflow to centralize maintenance

[tchataigner]

Do we also want to bump the Cargo.tomls for tests, examples, and cli/src/assets?

I believe that we should handle the proper versioning of the crates that are meant to be used as dependencies, so I wouldn't add them in my opinion.

[tchataigner]

LGTM!

[huitseeker]

This looks great! Just one comment on maintenability of a list of crates distinct from the workspace.

[huitseeker]

This is going to be a pain to maintain.
How about :

1. removing the glob in the members field of the [workspace] section in the top-level Cargo.toml,
2. installing tomlq in the CI machines using cargo-install,
3. do something like:

huitseeker@MacBook-Pro.localdomain➜~/tmp/sphinx(dev)» for i in $(tomlq workspace.members -f Cargo.toml|jq -r '.[] | "\"" + . + "\","'); do echo $i; done
"cli",
"core",
"derive",
"eval",
"helper",
"primitives",
"prover",
"recursion/circuit",
"recursion/compiler",
"recursion/core",
"recursion/gnark-ffi",
"recursion/program",
"sdk",
"tutorials",
"zkvm/*",

[samuelburnham]

Great idea, I used this up to date fork instead: https://github.com/cryptaliagy/tq-rs

[tchataigner]

LGTM, NIT about referring to environment variable in the same way ($MY_VAR vs ${{ env.MY_VAR }}