Reboot cometbft-rs versions as 0.1.0

[mzabaluev]

As we've got new crate names to release, we are free to restart the versioning.

[romac]

Given that we've been using these crates in many places for the past few years, how about rebooting with version 1.0 instead to signal the stability it now deserves imho? We can perhaps add a -alpha.N suffix until we've successfully integrated it in Hermes/ibc-rs/etc.

What do you think, @mzabaluev @sergio-mena @ancazamfir?

See comment above

[mzabaluev]

Given that we've been using these crates in many places for the past few years, how about rebooting with version 1.0 instead to signal the stability it now deserves imho?

The semver restrictions will apply to the Rust crates, including anything we have to change purely on the Rust side not connected to any changes in CometBFT in general. I don't have confidence at all that we are at the stage where we can commit to supporting the API at any long stretch of time, before we need to cut a new major version. With 0.x, we just bump the minor version instead like we always did.

Among other things, we need to have a prost-types vs. pbjson-types vs. roll-your-own showdown (see informalsystems/tendermint-rs#1053), and anything else that will fall out of the buf rework.

[romac]

I see what you mean, so yeah in any case we should stay at 0.x until we figure out the story around prost-types, but, etc. and also until we are able to confirm that cometbft-rs works for our purpose in Hermes.

After that, we can discuss whether or not we feel like the crate deserves at v1 or not. Keeping in mind that we can always release new major versions if needed, and do not have to commit to maintaining previous major versions indefinitely.

[mzabaluev]

In a call with @romac we have agreed to start with a pre-release version to test the release script.