Add EventRecorder and Scheme to MCPGroup controller

Summary

The MCPGroupReconciler struct has only a client.Client field — no Recorder, no Scheme. No Kubernetes events are recorded for MCPGroup state transitions. Every other controller (MCPServer, MCPRemoteProxy, EmbeddingServer, VirtualMCPServer) receives an EventRecorder.

Severity: MUST FIX
Area: Controller Logic
Breaking: No

Location

• cmd/thv-operator/controllers/mcpgroup_controller.go:30-32
• cmd/thv-operator/main.go:315-317

Problem

The MCPGroup controller has no way to emit Kubernetes events for its operations, unlike every other controller in the codebase.

Impact

• No Kubernetes events for MCPGroup operations (creation, deletion blocking, member changes)
• Reduced observability and debugging capability compared to other controllers

Recommended Fix

1. Add Recorder record.EventRecorder and Scheme *runtime.Scheme to MCPGroupReconciler struct
2. Pass mgr.GetEventRecorderFor("mcpgroup-controller") and mgr.GetScheme() in main.go
3. Record events for key state transitions

Start with cmd/thv-operator/controllers/mcpgroup_controller.go:30-32 and compare the MCPServer, MCPRemoteProxy, EmbeddingServer, and VirtualMCPServer controllers. Then inspect cmd/thv-operator/main.go:315-317 to follow how controller dependencies are passed. Done means MCPGroupReconciler receives the recorder and scheme and records events for creation, deletion blocking, and member changes.