Resolve versioning redundancy

In !102 (merged), we added a safety harness that chart_version == image_version. This is an important check, but not very ergonomic when combined with automatic versioning with semantic-release, because the contributor now needs to guess the eventual image version based on their commits.

Questions to resolve:

• Do auto-deploy-image and auto-deploy-app need to have the same version? If not, then we should still enforce image_version >= chart_version (because the image bundles the chart)
• If they do need to have the same version, can we have a single source of truth?
  • for example, by auto-updating the version in Chart.yaml with semantic-release

See also this discussion

/cc @dosuken123