fix(satellite): bridge controller-runtime logger to slog

cmd/satellite/main.go set up slog but never wired controller-
runtime's logr — so every log call from the c-r manager and the
per-CRD reconcilers (Resource, ResourceDefinition, Snapshot,
StoragePool, PhysicalDevice) was silently dropped.

Symptom: the satellite emitted only its three startup INFO lines
("blockstor-satellite starting", "agent starting", "satellite
controller-runtime manager ready"), followed by c-r's one-shot
goroutine dump warning that log.SetLogger was never called, and
then nothing — making it impossible to tell from the logs whether
reconcilers were running, returning errors, or sitting on a
blocked watch.

Hook logr.FromSlogHandler(logger.Handler()) into ctrl.SetLogger
so every reconcile event lands in the satellite's JSON log stream
next to the startup events. The controller binary already does
the same via zap (cmd/controller/main.go:105).

Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>

Author: kvaps

cmd/satellite/main.go

@@ -32,6 +32,7 @@ import (
 	"syscall"
 
 	"github.com/cockroachdb/errors"
+	"github.com/go-logr/logr"
 	"k8s.io/client-go/rest"
 	ctrl "sigs.k8s.io/controller-runtime"
 	"sigs.k8s.io/controller-runtime/pkg/manager"
@@ -64,6 +65,14 @@ func run() int {
 	logger := slog.New(slog.NewJSONHandler(os.Stderr, &slog.HandlerOptions{Level: slog.LevelInfo}))
 	slog.SetDefault(logger)
 
+	// Bridge controller-runtime's logr into our slog so every reconcile
+	// log from the c-r manager / per-CRD reconcilers shows up next to
+	// the satellite's own startup events. Without this c-r silently
+	// drops every log call (its `log.SetLogger(...) was never called`
+	// goroutine dump prints once on startup and reconciler errors
+	// disappear).
+	ctrl.SetLogger(logr.FromSlogHandler(logger.Handler()))
+
 	if nodeName == "" {
 		logger.Error("node-name is required (pass --node-name or set NODE_NAME)")