agent-platform release v4.133.0

Fixed

• A step that adds a connectivity values key no longer fails the connectivity release once on the previous chart (giantswarm/agent-platform#1019). Helm applies a HelmRelease before an OCIRepository, so a step handed its new values to helm-controller while the connectivity OCIRepository still held the previous chart, whose closed schema refused the added key (additional properties 'tenants' not allowed on the 4.131.1 → 4.132.0 step); the retry healed it, a release with no retry left stayed failed and its dependents not Ready. The connectivity OCIRepository is now named after its exact version (agent-platform-connectivity-<version>, agent-platform.sourceName), so the values and the chart version change in one HelmRelease spec change: helm-controller waits until the source of that name holds that version’s chart, then upgrades once; the previous source is pruned with the step. A dev channel or a range keeps the plain name. No installation needs to act.