feat: support explicit HyperDX Deployment and pod annotations

[mfroembgen]

Summary

• add hyperdx.deployment.deploymentAnnotations for HyperDX Deployment metadata
• add hyperdx.deployment.podAnnotations for HyperDX pod-template metadata
• retain hyperdx.deployment.annotations as a deprecated compatibility alias
• document and test that podAnnotations wins on duplicate legacy keys

Motivation

The existing hyperdx.deployment.annotations value configures spec.template.metadata.annotations, but its scope is ambiguous and there is no value for the Deployment object's metadata.annotations. Explicit names make both Kubernetes metadata surfaces clear without breaking existing installations.

Backward compatibility

The new values default to empty maps. Existing hyperdx.deployment.annotations values continue to render on the pod template. When both annotations and podAnnotations contain the same key, the explicit podAnnotations value takes precedence; non-conflicting legacy annotations are preserved.

Test plan

• helm unittest charts/clickstack — 28 suites, 190 tests pass
• focused HyperDX suite — 33 tests pass
• helm lint charts/clickstack
• default values and all three example values files render with Helm 3.12.0
• focused render confirms distinct Deployment and pod annotations plus compatibility merge precedence
• git diff --check

Fixes #254.

[changeset-bot]

🦋 Changeset detected

Latest commit: dd4a55b

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