fix: map DEBUG_MOVER annotation to LOG_LEVEL in mover Jobs

Start in internal/mover/ceph/job.go at the hardcoded LOG_LEVEL=info and the AppendDebugMoverEnvVar call, then compare the fallback handling in cmd/mover/main.go. Verify that the DEBUG_MOVER annotation results in debug-level mover logs while the default remains unchanged.

Problem

The VolSync debug-mover annotation (volsync.backube/enable-debug-mover) injects DEBUG_MOVER=1 into mover Jobs via utils.AppendDebugMoverEnvVar. However, the mover binary (cmd/mover/main.go) only reads LOG_LEVEL, and the Job hardcodes LOG_LEVEL=info (internal/mover/ceph/job.go:104).

As a result, setting the annotation on a ReplicationSource/ReplicationDestination CR does not raise mover log verbosity.

Expected

Annotating the CR should produce debug-level mover logs.

Suggested Fix

In internal/mover/ceph/job.go, after calling AppendDebugMoverEnvVar, check if DEBUG_MOVER=1 is present in the env list and set LOG_LEVEL=debug accordingly. Alternatively, have the mover binary read DEBUG_MOVER as a fallback.

References

• internal/mover/ceph/job.go:104 - hardcoded LOG_LEVEL=info
• internal/mover/ceph/job.go:280 - AppendDebugMoverEnvVar call
• cmd/mover/main.go:71 - envOrDefault(constant.EnvLogLevel, "info")