operator: Replace zap logger with global ContextFree logger

[RafalKorepta]

The multicluster command constructed its own ctrlzap.New() logger and passed it to RaftConfiguration.Logger, which forwarded it to the controller-runtime manager via ctrl.Options.Logger.

Because this logger had a non-nil sink, controller-runtime skipped the global logger fallback:

if options.Logger.GetSink() == nil {
    options.Logger = log.Log  // <-- never reached
}

The manager then used this raw zap sink to build per-reconciliation loggers in reconcileHandler:

log := c.LogConstructor(&req)
ctx = logf.IntoContext(ctx, log)

When reconciler code called otelutil/log.FromContext(ctx), which appends "ctx", ctx to keysAndValues, the zap sink serialized context.Context as the full wrapper chain:

"ctx":"context.Background.WithCancel.WithCancel.WithValue(logr...)"

The global logger set by main.go via log.SetGlobals(logger.NewLogger()) wraps non-OTEL sinks with ContextFree, which strips context.Context values from keysAndValues before they reach the underlying sink. But the per-command zap logger bypassed SetGlobals entirely, so it never got the ContextFree wrapper.

Fix by replacing the standalone ctrlzap.New() with log.FromContext(ctx), which retrieves the global logger already wrapped with ContextFree. Remove the now-unused --log-level flag and parseLogLevel helper, as log level is already configured globally via the root command's logOptions.

[andrewstucki]

Looks like the proper fix to me, probably want to name the logger based on the subsystem rather than the node though?