Tracking breaking changes

[koivunej]

While handling the latest 1.49 clippy lints in #667, there are at least two public instances of Result<_, ()> which are now nagged by clippy changing of which require a minor version bump:

• 2233dc9 (interledger-settlement)
• 170c9e7 (interledger-stream)
• 43728cf (interledger-store)
• whole of Bytes 05 upgrade #690 which updated bytes = "0.4" of interledger-packet which is re-exported
• stream: Allow fuzzing for Unknown Data (ErrorCode and FrameType) #719 changed interledger-packet::ErrorCode::new signature

Given commit 3f1a8de I had thought that 1.0.0 versions had already been pushed, but in light of us needing to make breaking changes to keep up with clippy, I'd recommend reverting the 1.0.0 bump and going ahead with the next released versions being 0.x series. crates.io doesn't have any 1.0 crates nor does dockerhub, at least as far as I can search it.

[koivunej]

As I already commented on the 667, we need a way to start marking the commits with breaking changes. I suggest conventional commits with ! in the scope and BREAKING CHANGE in the "footer". Also, we need to go back in time to find other breaking changes.

[kincaidoneil]

I'd recommend reverting the 1.0.0 bump and going ahead with the next released versions being 0.x series. crates.io doesn't have any 1.0 crates nor does dockerhub, at least as far as I can search it.

Sounds good to me 👍 (personally... wasn't a big fan of that "1.0" release)