setup ci action to simulate publishes

[Voxelot]

Troubleshooting CI failures during publish is difficult, as there is no way to test publishing without actually make a real publish.

We should have a custom action that allows us to simulate all the actions of a publish before officially tagging the release.

• allow user to set a custom publish tag via action input instead of creating a real tag
• use an ephemeral crate registry during the publish process
  • override the default registry for any dependencies between workspace members to use local registry
• skip docker image upload
• skip binary artifact upload

[adlerjohn]

use an ephemeral crate registry during the publish process

This is interesting. Would it be possible host an instance of crates.io (with the same validation rules) that we can use for this?

[xgreenx]

We use katyo/publish-crates@v2 action to publish all our crates, which supports dry-run. It performs most of the checks that should be done before publishing. It is not the same as publishing via cargo publish, but it should cover most cases.

We added a separate job publish-crates-check that will perform those checks before actual publishing.

We also can troubleshoot the problem locally. How to do that is described in this section.

I guess we can close the issue for now, but if it would be actual for us again, we can reopen it.