chore: switch out espresso fork of blst

[nomaxg]

I am working on integrating namespace proofs into Arbitrum and the Arbitrum prover relies on this crate that relies on another version of the native blst crate, resulting in the following compiler error:

   Updating git repository `https://github.com/EspressoSystems/tagged-base64.git`
error: failed to select a version for `blst`.
    ... required by package `jf-primitives v0.4.0-pre.0 (https://github.com/EspressoSystems/jellyfish#d9c1b634)`
    ... which satisfies git dependency `jf-primitives` of package `vid v0.1.0 (/Users/ngolub/Documents/projects/nitro-espresso-integration/arbitrator/wasm-libraries/vid)`
    ... which satisfies path dependency `vid` of package `jit v0.1.0 (/Users/ngolub/Documents/projects/nitro-espresso-integration/arbitrator/jit)`
versions that meet the requirements `*` are: 0.3.11

the package `blst` links to the native library `blst`, but it conflicts with a previous package which links to `blst` as well:
package `blst v0.3.11`
    ... which satisfies dependency `blst = "^0.3.11"` of package `c-kzg v0.4.0`
    ... which satisfies dependency `c-kzg = "^0.4.0"` of package `prover v0.1.0 (/Users/ngolub/Documents/projects/nitro-espresso-integration/arbitrator/prover)`
Only one package in the dependency graph may specify the same links value. This helps ensure that only one copy of a native library is linked in the final binary. Try to adjust you
r dependencies so that only one package uses the links ='blst' value. For more information, see https://doc.rust-lang.org/cargo/reference/resolver.html#links.

Switching out our fork for the crates.io hosted blst crate seems to solve this issue.

[mrain]

LGTM. Pending CI

[ggutoski]

Looks good, though I am curious why it was ever switched to our fork. See comment below.

[ggutoski]

This was originally changed to our fork in #254 . Prior to that it was

blst = "0.3.10"

@alxiong any reason for this switch? Any reason not to revert it now?

[mrain]

Probably for no_std. IIRC we have CI for it

[ggutoski]

CI fail for some reason. I successfully ran ./scripts/run_tests.sh on my local machine with no problem. 🤷

[mrain]

CI fail for some reason. I successfully ran ./scripts/run_tests.sh on my local machine with no problem. 🤷

This failure only happens with rust nightly build 2024-02-05, other's are experiencing it as well

we can force merge it if it's urgent

[nomaxg]

CI fail for some reason. I successfully ran ./scripts/run_tests.sh on my local machine with no problem. 🤷

This failure only happens with rust nightly build 2024-02-05, other's are experiencing it as well

we can force merge it if it's urgent

No rush, looks like there’s a pending fix this morning so I’ll rerun ci later.