Investigate migrating to Chart apiVersion v3 (Helm 4)

Description

Helm 4 introduces an experimental apiVersion: v3 Chart.yaml schema
(HIP-0020, accepted 2025-01-09) alongside the existing v1/v2. This
tracks investigating and eventually migrating this repo's charts
once it stabilizes.

Current state

All six charts (posit-chronicle, rstudio-connect,
rstudio-launcher-rbac, rstudio-library, rstudio-pm,
rstudio-workbench) use apiVersion: v2, which keeps working
unchanged under Helm 4. No action needed today.

What v3 is right now

• Opt in via HELM_EXPERIMENTAL_CHART_V3=1 +
  helm create --chart-api-version=v3
• Explicitly experimental — "use for testing and feedback only"
  (Helm 4 docs)
• No migration guide exists yet
• The v3 schema (internal/chart/v3/metadata.go) is currently
  field-for-field identical to stable v2 (pkg/chart/v2/metadata.go)
  — bootstrapped from v2, expected to diverge before GA

Next steps

Revisit when the upstream tracking issue closes or migration docs
are published.

References

• https://helm.sh/community/hips/hip-0020/
• https://helm.sh/docs/overview/
• https://github.com/helm/helm/issues/31738
• https://github.com/helm/helm/blob/main/internal/chart/v3/metadata.go
• https://github.com/helm/helm/blob/main/pkg/chart/v2/metadata.go

Start with HIP-0020, the Helm 4 documentation, and the upstream tracking issue referenced here; compare the v3 and v2 schema references noted in the issue. Review Chart.yaml for the six named charts only after upstream migration guidance exists. Done means the upstream schema is stable and a documented migration path is available.