agent-platform release v4.7.9

The Substrate line re-pins to v0.0.27-gs.4 (giantswarm/giantswarm#37757; giantswarm/giantswarm#37742 row 27): the release carries giantswarm/substrate#14 — an actor whose image the registry refuses for good (a digest answered 404, a repository the pull may not read) is crashed with the registry’s answer instead of being resumed against the same reference forever, and ate-api’s ActorTemplate reconciler records the cause on the template. A Harness whose workload.image cannot be pulled therefore fails its golden boot at once as Ready=False ActorTemplateFailed (GoldenActorCrashed: actor … crashed: … MANIFEST_UNKNOWN: manifest unknown) instead of sitting in ActorTemplatePending with a worker pinned for as long as anyone waits (measured at 300 s without a message on gs.2). components.substrate/components.substrate-crds move to >=0.0.27-gs.4 <0.0.28-0 and kagent.substrateWorkerPool.workerImage to …:0.0.27-gs.4; examples/customer-bom.yaml and tests/verify-components.py move with the pin. Asserted end to end in giantswarm/agent’s ATS on the release (test_fail_fast.py::test_unpullable_harness_image_fails_fast: 5 s, giantswarm/agent#34). No installation acts — the release stays inert behind the fleet’s <4.0.0 bound.