agent-platform release v4.61.1

A release whose component floor is unpublished is refused before either chart is pushed: make verify-release-floors, the strict run of tests/verify-components-charts.py on the tag pipeline (giantswarm/agent-platform#624). A floor bump merged before the component’s chart was pullable (klaus-gateway 1.20.0, tagged with a GitHub release while its chart pipeline had failed) produced 4.55.0, a release every installation on the line failed on twice over. On a tag the check resolves every components.<name>.versionRange and every BOM pin the way Flux does and pulls the chart it resolves to; UNRELEASED and RENDER_AGAINST do not apply there, and a range that admits nothing published, or a pin that is not published, fails naming the component and the version the release waits for. The connectivity push requires the job; the meta chart’s generated push-chart-release requires it through gen.ci.chartReleaseGateJob in giantswarm/github. Recovery is a rerun of the tag’s workflow from failed once the component chart is out — the tag stands. The branch pipeline keeps rendering against the fallbacks, so a PR can still land before the component release; without a fallback entry a PR bumping to an unpublished floor is red naming the version it waits for.