muster release v5.42.2

Fixed

• The Kubernetes watch’s startup listing no longer drops change events. At startup the detector emitted one event per existing MCPServer and Workflow into a 100-slot channel that the reconcile manager read only after the listing had synced, so on an installation with 289 Workflows everything past the first 100 was dropped with a Change event channel full WARN each, and a real change arriving during the listing could be lost the same way. The manager now drains the channel before the detector starts, and the detector waits for room instead of dropping, until it stops; each informer handler has its own unbounded buffer, so the wait paces only that handler. (#1469)