Monodeploy should handle duplicate git tag error scenario

[noahnu]

Describe the bug

If a git tag is pushed and then before committing package.json changes (in noRegistry mode) the publish fails for whatever reason, we end up in a sitatuation where the next publish will fail because the tag already exists.

Expected behavior

Not sure how best to handle this.