Release on crates.io

[0xForerunner]

I think it makes sense for reth, including all of its crates, to begin releasing to crates.io.

Although the reth versioning system isn't semver compatible, we could still offer a way to make patch versions compatible with each other for library consumers.

Example

1.5.1 is not compatible with 1.6.0
1.5.1 is compatible with 1.5.2 (No breaking changes in the api)

To achieve this behaviour we can instruct consumers to use ~ in Cargo.toml to lock to minor version. See this excerpt from the rust book:

~1.2.3  := >=1.2.3, <1.3.0
~1.2    := >=1.2.0, <1.3.0
~1      := >=1.0.0, <2.0.0

I've personally run into this issue a handful of times when using external dependencies that rely on reth via git, but the patch version is different.

[0xForerunner]

Actually, now that I'm thinking about this more, perhaps it makes sense to decouple binary versions with lib versions, since currently 1.0 is not yet published on crates.io.

reth-network = "0.1.0" -> reth = "1.5.1" 

This way we are consistent with semver on crate.io