feat: Release container images into Github Packages repository

[migmartri]

Update goreleaser to also build container images with latest versions of the binary inside pushed to Github packages repository ghcr.io/vmware-tanzu/asset-relocation-tool-for-kubernetes

The Dockerfile has also been updated to leverage the binary created by goreleaser itself

Tested it and an image was built and pushed as expected https://github.com/vmware-tanzu/asset-relocation-tool-for-kubernetes/pkgs/container/asset-relocation-tool-for-kubernetes/13030106?tag=v0.3.61-pre https://github.com/vmware-tanzu/asset-relocation-tool-for-kubernetes/actions/runs/1683473654

Refs #127

[vmwclabot]

@migmartri, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 4e7e412 must be signed by mtrivino@vmware.com

[petewall]

LGTM

[petewall]

Does this mean the image is living here and not on projects.registry.vmware.com/tanzu_isv_engineering/relok8s? We should update the pipeline.yaml to find the image in the right location, then.

[migmartri]

yeah, sorry, I missed linking the task #127

This whole task started because I noticed that we are no longer building the external container images since we've moved the release process outside.