muster release v5.27.7

Fixed

• A session connecting to an MCPServer no longer reconciles it. With the reconciler’s duplicate cadence gone (#1285), every server was still reconciled – and its CR status written – once per session that connected to it: the aggregator reports each successful session connection to api.UpdateMCPServerState, which queued a reconcile unconditionally, so every new session’s SSO fan-out cost one pass per server it reached, several times per ten minutes on a busy installation, while nothing changed. The handler now only hands the state to the service. A state that actually changes (Auth Required to Connected on the first session, back on the last session’s loss) reaches the CRD status through the service’s state-change event and the StateChangeBridge, as every other state change does; an unchanged state is logged at debug and costs nothing. TriggerReconcile is gone from the reconcile manager’s API; it had no other caller. (#1290)