Better handling of stable/1.0 crates

[Byron]

Currently one has two options:

• use --auto-publish-of-stable-crates to safety-bump stable crates just like unstable ones, causing unnecessary churn downstream
• not do the above and see the publish fail as the manifest wasn't updated with new/bumped versions of workspace dependencies.

What would be required is the give them a patch-level bump instead, while keeping everything else as is (maybe even by default). That way they could be published as usual and everything should work fine.

[brooksmtownsend]

@Byron could you elaborate a bit here on the issue, is it that by default we attempt to bump 1.0.0 crates to 2.0.0? or 1.1.0 instead of a patch version?

[Byron]

gitoxide crates are already suffering from this issue, as auto-publish-of-stable-crates is default-off now, just to avoid surprises, but the result of the operation might be then be somewhat incorrect (i forgot details). So these days, I just enable it and indeed auto-bump stable crates, quite a terrible thing to do.

It's definitely something to fix once gix wants to go 1.0.