muster release v5.27.4

Fixed

• An MCPServer in sync is left alone. In Kubernetes mode the reconciler logged Reconciling MCPServer: <name> for every server about every 14 s – some 250 passes per server per hour, each a definition read and a status write against the API server, while nothing changed. Two periodic sources of the same length ran out of phase: every successful pass requeued itself after 30 s (the status sync from before the periodic resync existed), and the Manager’s resync enqueued every server every 30 s on top. A pass that finds the server in sync now asks for nothing further – the next one comes from a definition change, a runtime state change (StateChangeBridge) or the resync – and the resync is a safety net for a lost event rather than a heartbeat: its default is ten minutes instead of 30 s. MUSTER_RECONCILER_RESYNC_INTERVAL still overrides it and muster test still runs instances at 2 s. DefaultStatusSyncInterval is gone. (#1285)