UX: Do not show same image relocation twice

[migmartri]

For example, the following command shows the same relocation twice, it should be enough to show it once.

 harbor-repo.vmware.com/tanzu_isv_engineering/tiny:tiniest => projects.registry.vmware.com/relocated/example2/tiny:tiniest (sha256:adf10351862ad5351ac2e714e04a0afb020b9df658ac99a07cbf49c0e18f8e43) 

$ relok8s chart move --image-patterns ./test/fixtures/testchart.images.yaml --registry projects.registry.vmware.com --repo-prefix relocated/example2 ./test/fixtures/testchart/
Computing relocation...

Image copies:
 harbor-repo.vmware.com/tanzu_isv_engineering/tiny:tiniest => projects.registry.vmware.com/relocated/example2/tiny:tiniest (sha256:adf10351862ad5351ac2e714e04a0afb020b9df658ac99a07cbf49c0e18f8e43) (push required)
 harbor-repo.vmware.com/tanzu_isv_engineering/tiny:tiniest => projects.registry.vmware.com/relocated/example2/tiny@sha256:adf10351862ad5351ac2e714e04a0afb020b9df658ac99a07cbf49c0e18f8e43 (sha256:adf10351862ad5351ac2e714e04a0afb020b9df658ac99a07cbf49c0e18f8e43) (push required)
 harbor-repo.vmware.com/dockerhub-proxy-cache/library/busybox:1.33.1 => projects.registry.vmware.com/relocated/example2/busybox@sha256:b862520da7361ea093806d292ce355188ae83f21e8e3b2a3ce4dbdba0a230f83 (sha256:b862520da7361ea093806d292ce355188ae83f21e8e3b2a3ce4dbdba0a230f83) (push required)
 harbor-repo.vmware.com/tanzu_isv_engineering/tiny:tiniest => projects.registry.vmware.com/relocated/example2/tiny:tiniest (sha256:adf10351862ad5351ac2e714e04a0afb020b9df658ac99a07cbf49c0e18f8e43) (already exists)

[josvazg]

What should be the criteria to pick the shown?

• Should the first of the list?
• Show the rolling one? or the one with the @sha?

Also skipping those might be misleading, as those move are different tags tiny:tiniest vs iny@sha256:ad... they are in a way different updates, even if one is just an alias. Omitting might create confusion to consumers not knowing of the the tags was applied?

[petewall]

Related to #80