Verify that an ARO-HCP change renders in the sdp-pipelines EV2RA generator before it ships, in the same way the ADO "Generate Ev2 Manifests" step does.

Why this exists

ARO-HCP's own CI (make verify, templatize pipeline validate, config make validate, helm-test fixtures) renders every template with concrete config values, so it PASSES even when a change breaks the sdp-pipelines EV2RA generator.

The generator renders Helm values.yaml, *.bicepparam, and pipeline.yaml in resolve mode, where every config reference becomes the literal "dunder" string __path.to.value__ (EV2 substitutes the real value at deploy time). Anything that treats a referenced config value as a real type then explodes. The canonical failure was a values.yaml doing {{ range .hypershift.metricsSet.extraHCPMetrics }} — fine with a real array, but under resolve:

check-ev2-render

Why this exists