extra/monitoring defaults logsStorages to the LINSTOR-only "replicated" StorageClass #3388

Symptom

On a Cozystack install without LINSTOR — in particular the isp-hosted platform variant, where storage is provided by the host — the root tenant's monitoring logs PVC stays Pending forever, because it requests a StorageClass that does not exist on the cluster.

Mechanism

packages/extra/monitoring/values.yaml defaults logsStorages[0].storageClassName to replicated. No chart in this repository creates a StorageClass named replicated; it is provisioned out of band by LINSTOR (see hack/e2e-post-install-prep.sh). The isp-hosted variant emits no LINSTOR at all.

monitoring.rootEnabled defaults to true in packages/core/platform/values.yaml, and values-isp-hosted.yaml does not override it. packages/apps/tenant/templates/monitoring.yaml passes no storage override, so the default reaches the tenant chart unchanged.

The host-side stack is unaffected — packages/system/monitoring/values.yaml uses storageClassName: "" (cluster default) for the equivalent fields. The hardcoded replicated appears only on the extra/monitoring path.

Suggested fix

Default logsStorages[].storageClassName to "" so it follows the cluster default StorageClass, consistent with the other storage fields in the same file and with system/monitoring. Operators who want the LINSTOR-backed class can set it explicitly, and the isp-full presets can carry that value where it belongs.

Notes

Found while reviewing the fix for #3376. Same class as the unguarded Cilium policies in apps/tenant filed alongside this: a hosted-unaware default that stayed invisible while the isp-hosted system bundle was disabled and nothing on that path was ever installed.