Cargo release blocks with Waiting for publish to complete... when using alternative registry

[metaclips]

Using alternative registry estuary, cargo-release blocks while publishing workspace packages. This seems to be due to cargo release searching crates.io as the source of truth if the crate has been updated.

[epage]

Yes, we need

• To read the users registry like cargo does
• Support for waiting for registries besides the default

In the mean time, you can specify the registry in your release.toml.

[epage]

With cargo now blocking, we've instead stopped blocking ourselves. See #743