Web app doesn't pick Template ConfigMaps because they miss labels

[kimwnasptd]

Bug Description

Right now the katib-web-app will not allow users to select a TrialTemplate, when creating a new Experiment, even though we do deploy TrialTemplates as configmap

katib-operators/charms/katib-controller/src/charm.py

Lines 309 to 322 in 10f75f9

	"trial-template": {
	f
	+ suffix: render_template(
	f"src/templates/{f}.yaml.j2", self.images_context
	)
	for f, suffix in (
	("defaultTrialTemplate", ".yaml"),
	("enasCPUTemplate", ""),
	("pytorchJobTemplate", ""),
	)
	},
	},
	},
	)

To Reproduce

Deploy latest track/0.15 Katib Charms (controller and ui)

Environment

latest/edge as well as track/0.15

Relevant Log Output

No logs from Charms or the app

Additional Context

No response

[kimwnasptd]

This is because the backend of the Katib web app will only filter ConfigMaps that have a label katib.kubeflow.org/component: trial-templates
https://github.com/kubeflow/katib/blob/e3e0aa24aeea1edfab0fd42f55392af651d2b3ae/pkg/util/v1beta1/katibclient/katib_client.go#L169

But we don't add any labels when we create the ConfigMap. We'll need to update our Charm to add this label to created ConfigMap

[kimwnasptd]

we found this while looking into having one simple TrialTemplate in CKF for #132