Clean up `git` dependencies

[ggwpez]

### Tasks
- [x] [simple-mermaid](https://github.com/kianenigma/simple-mermaid) used [here](https://github.com/paritytech/polkadot-sdk/blob/b51904da5681c479e462ab0b5bdd7464dfecd27a/docs/sdk/Cargo.toml#L25)
- [x] [ethabi-decode](https://github.com/snowfork/ethabi-decode) used [here](https://github.com/paritytech/polkadot-sdk/blob/127b9bec15f8a83964ef6049209df75da47b1479/bridges/snowbridge/parachain/pallets/system/Cargo.toml#L36)
- [ ] [bandersnatch_vrfs](https://github.com/w3f/ring-vrf) used [here](https://github.com/paritytech/substrate/blob/e966352d118a745678f720ae85e617d054dc8165/primitives/core/Cargo.toml#L62)
- [x] [milagro_bls](https://github.com/snowfork/milagro_bls) from [here](https://github.com/paritytech/polkadot-sdk/blob/bab0348372b58d5106333faa597423242e831a31/bridges/snowbridge/parachain/primitives/beacon/Cargo.toml#L34)

[davxy]

For bandernatch (cc @swasilyev):

• Publish https://github.com/w3f/fflonk
• Publish https://github.com/w3f/ring-proof
• Introduce ark-ec-vrfs

[bkontur]

there is also an issue for ethabi-decode here: paritytech/parity-bridges-common#2775
(afaik, Vincent will work on it)

cc: @vgeddes @claravanstaden

[vgeddes]

Ack, yes, I'll publish ethabi-decode and milagro-bls this week. Thanks for the reminder.

[vgeddes]

I've published them:

• https://crates.io/crates/ethabi-decode
• https://crates.io/crates/snowbridge-milagro-bls

We will update our cumulus/bridges/snowbridge subtree next week which will include these changes.

[Morganamilo]

From a crates perspective. Our tooling with auto strip optional git depends or switch git dependencies to crates.io if a compatible version exists. Meanwhile git deps with no crates.io releases are totally unpublishable. So releasing milagro_bls is high priority to me as it made some crates unpublishable on the last release.

[claravanstaden]

@Morganamilo thanks for the info. As @vgeddes mentioned, the crates are published and I have updated their usages in this PR: #3029

[ggwpez]

@Morganamilo Which crates would still blocked after #3029 and by what?

[Morganamilo]

That was the only crate I had issue with. Checking again, it was named milagro_bls on my end but I only see snowbridge-milagro-bls on crates.io. I guess the crate was renamed but that didn't make the release window and I got the old name?

[claravanstaden]

Exactly, @Morganamilo.

[claravanstaden]

Hey @Morganamilo! I was expecting the snowbridge crates to be updated with the polkadot-sdk 1.7.0 release, but it looks like the crates are still empty: https://crates.io/crates/snowbridge-pallet-inbound-queue/0.0.0

Will you let know if there is an issue with the publishing, or any other problem?

[ggwpez]

I think the crate publishing takes a while - we are also rate limited by crates-io. You can check here if stuff is being published https://crates.io/users/parity-crate-owner?sort=recent-updates

[Morganamilo]

Is there anything blocking simple mermaid? Would moving to 0.1.1 work or do we need features that are unreleased?

[ggwpez]

Yea 0.1.1 should include my fix.
I will try to remove it here in the repo. PS: #3304