Avoid dirtying the tree when removing dev-deps

[Manishearth]

cargo workspaces publish, when publishing crates with cyclic dev deps, will helpfully remove the dev-dependencies section before publishing.

Unfortunately, this leads to a "dirty" publish, which gets included in the cargo VCS info file. It would be nice if we had an option to make commits each time it dirties the tree.

Note that removing dev-deps will also trigger a lockfile change (which I believe also dirties the tree?), so the step should probably be "remove dev deps", "regen lockfile" (probably by running cargo package), "make a commit", and then "publish".

[pksunkara]

I assume that the commit would be throwaway, righ?

[Manishearth]

No, people would want to retain it somewhere so that people using cargo_vcs_info can find it on the repo. A dirty cargo_vcs_info is not that different from a cargo_vcs_info that points to a nonexistant commit.

I recommend making a series of commits following some pattern (here's an example: unicode-org/icu4x@2a279cc). They may not be the kind that people want on main, but people would want them somewhere.

Or perhaps have --dev-dep-commit-pattern="temporarily remove dev-deps on {crate} for release".

We might want to print a warning asking people to revert the commits afterwards, though.

[Manishearth]

n.b. for people dealing with this: cargo workspaces publish --from-git --no-remove-dev-deps will let you start a release, have it get interrupted by cyclic dev deps, fix the dev dep, and continue withe the command