We currently ignore the spec.addons.<addon>.install.service.ingress.metadata field for Kiali and Jaeger add-ons. This issue is about implementing it.

From https://docs.google.com/document/d/13Z7IPQRXVIWGpFzqU9woRT_nr1bE8mcs1Nvq_2rrvkk/edit#heading=h.m8306jv8lurg

• Jaeger CR theoretically supports setting annotations and labels in its spec.ingress but we don’t do that (and I don’t know if it really works)
• Kiali CR supports setting labels directly, and a full override (.spec.deployment.ingress.override_yaml) but we don’t do either

Acceptance Criteria:

• support setting annotations and labels on Routes for Kiali and Jaeger
• operator unit test