fix: move PKI_PATH to defaultCR env

[gmlexx]

Due to mergeOverwrite in opentelemetry-kube-stack chart we cannot customize individual collector env independently from defaultCR env without loosing defaultCR env.

[Copilot]

Pull request overview

This PR fixes an issue with environment variable configuration in OpenTelemetry collectors caused by the mergeOverwrite behavior in the opentelemetry-kube-stack chart. The PKI_PATH environment variable is moved from individual collector configurations to the defaultCRConfig.env section to prevent loss of default environment variables when customizing individual collectors.

Changes:

• Relocated PKI_PATH environment variable from individual collector specs to defaultCRConfig.env across demo files and chart values
• Implemented custom merge logic in child multi-cluster service template to properly concatenate environment variables instead of overwriting them
• Updated chart defaults to set PKI_PATH at the defaultCRConfig level with value var/lib/k0s

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
demo/collectors-values.yaml	Moved PKI_PATH from collectors.controller-k0s.env to defaultCRConfig.env
demo/cluster/adopted-cluster-regional.yaml	Added PKI_PATH environment variable to defaultCRConfig.env for regional cluster
demo/cluster/adopted-cluster-child.yaml	Added PKI_PATH environment variable to defaultCRConfig.env for child cluster
charts/kof-collectors/values.yaml	Relocated PKI_PATH from controller-k0s.env to defaultCRConfig.env with default value
charts/kof-child/templates/child-multi-cluster-service.yaml	Implemented custom environment variable concatenation logic to preserve default env vars when merging collector values