[HDX-4664] Use a dedicated Replicated otel database for fresh installs

[SpencerTorres]

Summary

Fresh installs with the bundled ClickHouse now use a dedicated otel database, created by the collector's migration as Replicated with Replicated* tables. Existing installs keep their current database and engines.

Draft until upgraded HyperDX collector ships (hyperdxio/hyperdx#3309) (adds the replicated migration) and the Update App Version PR for 2.x.x is merged. With the current collector image, otel would be created with plain engines.

How it works

Install	Database	Engines	HyperDX sources
Fresh install	otel	Replicated	otel
helm upgrade	Unchanged (default)	Unchanged	Unchanged
ArgoCD / helm template upgrade	Collector stays on default via fallback	Unchanged	Existing unchanged
External ClickHouse	default	Unchanged	default

Upgrades are detected with a lookup of the existing clickstack-config ConfigMap. Renders without cluster access can't see it, so the collector falls back to default when it finds existing ClickStack tables there.

Known limitations

• After an ArgoCD / helm template upgrade, teams created later get default sources on otel. Pin HYPERDX_OTEL_EXPORTER_CLICKHOUSE_DATABASE: "default" to avoid this (documented in UPGRADE.md).
• Existing installs stay non-replicated. Moving them is a manual step.

Test Plan

• helm unittest (270 tests) and helm lint
• kind with the ClickHouse operator, standalone and supervisor mode: upgrade from 3.4.0, ArgoCD-style render, fresh install, scale to 2 replicas

[changeset-bot]

🦋 Changeset detected

Latest commit: 388fd75

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
helm-charts	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR