CLI: "deploy/publish" commands should not ask to bump version if tag already exists

[theduke]

Currently, when running wasmer deploy with an unchanged named package, the CLI will:

• build the package locally
• Upload it if it does not exist in the backend
• Ask to bump the version ( => tag new version)
• Deploy

If the package already has a version matching the package hash, the "ask to bump" step should be skipped, and the matching version should be used.

There should potentially be a warning/confirm step if the version number in wasmer.toml does not match the auto-determined version.

[theduke]

Relevant backend query:

{
  getPackageVersionByHash ()
}