Add billing to services

[zugao]

Summary

• Added a label to each of our services to allow easy scrape of billing metrics

Checklist

• Categorize the PR by setting a good title and adding one of the labels:
  bug, enhancement, documentation, change, breaking, dependency
  as they show up in the changelog
• Update tests.
• Link this PR to related issues.

[wejdross]

build is also failing and needs to be fixed

[TheBigLee]

Please also fix the failing build action

[wejdross]

This code won't work if we have multiple deployments/statefullsets in single instance namespace, but that was never in acceptance criteria, therefore I'll aproove that.

[zugao]

This code won't work if we have multiple deployments/statefullsets in single instance namespace, but that was never in acceptance criteria, therefore I'll aproove that.

This is exactly the reason why this PR exists, to filter other deployments/statefulsets. Currently we have 2 deployments for nextcloud, one for the service itself and one for the metrics and with current code we count nextcloud twice into billing. I understand that in the future other deployments and statefulsets might reside into the instance namespace that HAVE to be counted towards billing but this is not the case right now and we should never implement something for the future as we don't know how it will look like from requirements point of view.

Update: the point is simple, we cannot know which statefulsets/deployments must be billed, metrics - no, collabora - yes, X no or yes? this has to be done when a new deployment/staefulset is added.