agent-platform release v4.85.0

Changed

• A targeted release (gitops.target.kubeConfig) names its children per target and installs them into a namespace of the platform’s own (giantswarm/agent-platform#688). Each OCIRepository and HelmRelease on the installation is <gitops.target.name>-<component> (gitops.target.name is new; empty means the release name), and so is every dependsOn and chartRef. Two targeted releases in one namespace (two workload clusters of one organization) no longer collide. Each child’s Helm release keeps the component’s name. gitops.targetNamespace now defaults to agent-platform with the knob, and the Helm storage follows it (storageNamespace), so nothing lands in the organization namespace on the target any more. Without the knob, the render is unchanged. A targeted release rendered by an older chart renames its children on upgrade: Flux uninstalls the old ones from the target and installs the new ones into the new namespace.