in order to make the installation of Cartographer in carvel-based
packaging easier, we used to have this secret that gets filled by
secretgen-controller as part of the set of objects shipped in the
release, but given that it's such a packaging-specific detail, here we
get rid of it favoring `package-for-cartographer` as the location for
doing so.

see vmware-tanzu/package-for-cartographer#23 for
the PR where that addition of a secret to the package takes place (file:
src/cartographer/config/overlays/image-pull-secret.yaml)

Signed-off-by: Ciro S. Costa <ciroscosta@vmware.com>

when installing cartographer, such object is not included anymore, so it
wouldn't show up in the list of objects that kapp is managing

Signed-off-by: Ciro S. Costa <ciroscosta@vmware.com>

any carvel packaging related to cartographer now takes place under
`vmware-tanzu/package-for-cartographer`, so, get rid of this leftover.

Signed-off-by: Ciro S. Costa <ciroscosta@vmware.com>

we used to bring up the registry with authentication enabled so that we
could be sure that the packaging work was right w/ regards to providing
credentials via secretgen's placeholder secrets, but now that such
responsability has shifted towards the packaging efforts under
`vmware-tanzu/package-for-cartographer`, we can now get rid of this
requirement from this repository

Signed-off-by: Ciro S. Costa <ciroscosta@vmware.com>

with the registry used by those not requiring any more auth, we can get
rid of those credentials from the setup.

Signed-off-by: Ciro S. Costa <ciroscosta@vmware.com>

with the removal of the need for authenticating against the registry
where we publish the release of cartographer, we can now skip all the
references to the previously `hack/registry-auth` directory where a
secretexport was placed for the credentials to the local registry

Signed-off-by: Ciro S. Costa <ciroscosta@vmware.com>

Signed-off-by: Ciro S. Costa <ciroscosta@vmware.com>