Improved deployment strategies for image repositories

**Community Note**
* Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**

Automatic deployments aren't really automatic for image repositories. From what I understand you must have an image tagged 'latest' and if I want a Service to automatically update you need to replace the 'latest' image with a newer image. This is not "automatic" and not consistent with continuous deployment standards.

It would be preferable to configure the update strategy to be used for each image individually, with the default being the `semver`strategy.

**Describe alternatives you've considered**
The following update deployment strategies should be supported:

semver - Update to the latest version of an image considering semantic versioning constraints
latest - Update to the most recently built image found in a registry (not based on 'latest' tag).
digest - Update to the latest version of a given version (tag), using the tag's SHA digest
name - Sorts tags alphabetically and update to the one with the highest cardinality

**Additional context**
This is the standard practice of continuous deployment tools like...

[Argo CD](https://argocd-image-updater.readthedocs.io/en/stable/#features)
[Flux CD](https://fluxcd.io/flux/guides/image-update)