Use consistent labelling

[a-thaler]

Description

Use a consistent module label and common label selectors for the telemetry-manager and its resources.

Criterias

• All resources of the module can be found by a simple label selector defining the module name
• All resources of the module are following labelling best practices
• Align with Consistent labeling of kyma modules community#864.
• There should be one central place where the labels/selectors are defined.
• Check if we should use the commonLabels construct in the kustomization config.

Implementation
The story should be split into the resources part of the module resources managed by lifecycle-manager/user and the resources managed by the telemetry-manager. Changing the labels will be a problem for podSelectors which are immutable fields, so all workload needs to be re-created.

• Module resources
  • Rename the telemetry-manager and change the podSelector labels as part of Rename telemetry-operator to telemetry-manager #651
  • Rename all labels in the module resources (Apply consistent labelling for kustomize managed resources #874)
  • Add "module" label (Introduce the kyma-project.io/module=telemetry label for all Telemetry module resources #1783)
• Manager resources
  • Rename the telemetry collector and change the podSelector labels as part of Rename trace-collector to trace-gateway #652
  • Rename podSelectors for metric gateway and metric agent
  • Rename all labels of trace/metrics domain
  • Rename podSelector for fluent-bit
  • Rename all labels of log domain

[a-thaler]

The istio module applied labelling already, see https://kyma-project.io/#/istio/user/00-10-overview-istio-controller?id=labeling-resources

[github-actions]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.