Publish Harbor as a Carvel package

[100mik]

Folks using Carvel's kapp-controller will be able to install Harbor as an independent Carvel package if we wrap the existing helm chart into a Carvel package and publish it.

Users who do not use Carvel today might find benefits as well,

1. Carvel prevents drifting of configuration - it reconciles to ensure that desired state is maintained.
2. It would allow users to define PackageInstallations declaratively, thus allowing them to set up[ Harbor on their cluster in a GitOps-ey fashion
3. A Carvel package can be easily moved into an air-gapped environment

If we automate the process of releasing a Carvel package (with the existing Helm chart bundled inside it) as a part of the release process it will require minimal or maintenance!

What would be the next steps if we move forward with this?