[CONTP-2114] send config in helm metadata as json vs yaml

[nlchung]

What does this PR do?

Changes the Helm release configuration fields in the operator's Helm metadata forwarder payload (helm_provided_configuration, helm_full_configuration) from YAML-serialized strings to JSON-serialized strings.

Motivation

CONTP-2114: the outbound datadog_operator_helm_metadata payload is JSON everywhere except these two fields, which were serialized with yaml.Marshal instead of json.Marshal. This made the values harder to query/parse downstream (e.g. in Metabase) since consumers have to YAML-parse a string field instead of reading normal JSON.

Additional Notes

ReleaseSnapshot/HelmReleaseData/HelmMetadata fields ProvidedValuesYAML/FullValuesYAML are renamed to ProvidedValues/FullValues. They remain string-typed; the change is in how the value itself is produced (json.Marshal instead of yaml.Marshal), so helm_provided_configuration/helm_full_configuration are still emitted as JSON string fields in the payload, but the string content is now JSON-formatted instead of YAML-formatted.

Describe your test plan

• go test ./pkg/controller/utils/metadata/... — existing suite updated and passing.
• Manually verified the outgoing payload shape via a local test that calls buildSnapshot/buildPayload directly and prints the JSON, confirming helm_provided_configuration/helm_full_configuration now contain JSON-formatted content instead of YAML.
• Manually verified in PUP that the field is now appearing in json as intended

Checklist

• PR has at least one valid label: bug, enhancement, refactoring, documentation, tooling, and/or dependencies
• PR has a milestone or the qa/skip-qa label
• All commits are signed (see: signing commits)

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-22T18:43:51.513993Z	12bf563	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.