Clean up various kubernetes profiles config about quarkus-super-heroes

[edeandrea]

Actually @holly-cummins I'm not sure that the multiple-profiles thing actually helps clear this up at all because we're still only talking about the default profile...

quarkus.kubernetes.part-of=villains-service
quarkus.kubernetes.annotations."app.openshift.io/connects-to"=villains-db,otel-collector
quarkus.kubernetes.env.configmaps=${quarkus.application.name}-config
quarkus.kubernetes.env.secrets=${quarkus.application.name}-config-creds
quarkus.kubernetes.labels.app=${quarkus.application.name}
quarkus.kubernetes.labels.application=${quarkus.kubernetes.part-of}
quarkus.kubernetes.labels.system=quarkus-super-heroes

quarkus.openshift.part-of=${quarkus.kubernetes.part-of}
quarkus.openshift.annotations."app.openshift.io/connects-to"=villains-db,otel-collector
quarkus.openshift.env.configmaps=${quarkus.kubernetes.env.configmaps}
quarkus.openshift.env.secrets=${quarkus.kubernetes.env.secrets}
quarkus.openshift.labels.app=${quarkus.kubernetes.labels.app}
quarkus.openshift.labels.application=${quarkus.kubernetes.labels.application}
quarkus.openshift.labels.system=${quarkus.kubernetes.labels.system}

the problem is that there isn't (that we know of or is documented anywhere) any kind of inheritance between the quarkus.kubernetes.* namespace and others (quarkus.openshift.*, quarkus.minikube.*, quarkus.knative.*, etc)

[holly-cummins]

Oh, good point!

[edeandrea]

This will depend on quarkusio/quarkus#34487 and quarkusio/quarkus#34025

[edeandrea]

Based on quarkusio/quarkus#34487 and quarkusio/quarkus#34025, the implementation of this will change a bit. We will define everything at the quarkus.kubernetes and then only add quarkus.openshift/minikube/knative/etc for things that need to be overridden, or that don't exist in quarkus.kubernetes.*.