feat(telemetry): add cluster dimensions to diagnostics

[juliobguedes]

What is the purpose of this pull request?

Add Kubernetes cluster identity and role as shared diagnostics resource attributes:

• VTEX_CLUSTER_ID → cluster_id
• VTEX_CLUSTER_ROLE → cluster_role

The values are trimmed, omitted independently when empty, and applied centrally to diagnostics metrics and logs without consuming per-call custom attribute limits.

What problem is this solving?

Diagnostics telemetry could not be grouped or filtered by its originating Kubernetes cluster, making cross-cluster dashboards and incident isolation harder.

How should this be manually tested?

• yarn build
• yarn lint
• yarn test --runInBand
• Start the service with VTEX_CLUSTER_ID and VTEX_CLUSTER_ROLE, then confirm the diagnostics resource attributes contain cluster_id and cluster_role.

Screenshots or example usage

Not applicable.

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Requires change to documentation, which has been updated accordingly.

[sonar-workflows]

Quality Gate failed

• 316 New Issues (is greater than 0)
• 30.60% Coverage on New Code (is less than 75.00%)
• 0.00% Security Hotspots Reviewed on New Code (is less than 100.00%)
• D Reliability Rating on New Code (is worse than A)

Project ID: node-vtex-api

View in SonarQube