aggregator custom labels template

[jessegoodier]

What does this PR change?

Adding aggregator custom labels template
It is a helm best practice, andwe need it for some monitoring requirements

Does this PR rely on any other PRs?

No

How does this PR impact users? (This is the kind of thing that goes in release notes!)

added aggregator custom labels helm template

What risks are associated with merging this PR? What is required to fully test this PR?

NA, following best practices found in other helm charts

How was this PR tested?

Tested with and and without the additional label. Label does not impact selector.

Have you made an update to documentation? If so, please provide the corresponding PR.

added to values file, which is all we need.

[jessegoodier]

/cherry-pick v2.4

[thomasvn]

This LGTM. It also seems to follow the existing pattern for adding labels to services.

cost-analyzer-helm-chart/cost-analyzer/templates/cost-analyzer-service-template.yaml

Lines 8 to 11 in 09bf88b

	{{- include "cost-analyzer.commonLabels" . | nindent 4 }}
	{{- if .Values.service.labels }}
	{{ toYaml .Values.service.labels | indent 4 }}
	{{- end }}

cost-analyzer-helm-chart/cost-analyzer/templates/prometheus-server-service.yaml

Lines 11 to 14 in 09bf88b

	{{- include "prometheus.server.labels" . | nindent 4 }}
	{{- if .Values.prometheus.server.service.labels }}
	{{ toYaml .Values.prometheus.server.service.labels | indent 4 }}
	{{- end }}

cost-analyzer-helm-chart/cost-analyzer/templates/frontend-service-template.yaml

Lines 8 to 11 in 09bf88b

	{{- include "cost-analyzer.commonLabels" . | nindent 4 }}
	{{- if .Values.service.labels }}
	{{ toYaml .Values.service.labels | indent 4 }}
	{{- end }}

[jessegoodier]

/cherry-pick v2.4