Capture image metas information in imgpkg lock file and ensure it's consumed properly

[aaronshurley]

Describe the problem/challenge you have
This issue is in support of a larger (i.e. multi-tool) functionality. From that issue:

When deploying packages with imgpkg bundles the tag of a container is replaced with sha256 in a deployed pod/deployement/daemonset. This is a challenge for serviceability when I need to figure out what tag of a container is deployed. It requires me look at the sha and comparing in registry and if I don't have access to registry then I have to expand the imgpkg bunde retrived from Package CR and look in .images.yml

Describe the solution you'd like
From the originating issue:

Add a kapp annotation with the tag of the container on the Pod/Deployment/Daemonset objects.

A human-readable annotation that states the "source" tag. For kbld, this would likely mean adding additional metadata to the imgpkg lock file.

Anything else you would like to add:
Please familiarize yourself with the originating issue to ensure that this is all that would be needed from kbld.

---

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.