When creating an SBDConfig without specifying an image, the Operator injects a default image path from its environment variables. This default path is invalid, causing the Agent pods to fail permanently with ImagePullBackOff / ErrImagePull.

Investigation reveals two errors in the default path registry.redhat.io/workload-availability/sbd-agent:latest:

1. Repository Name Mismatch: The operator attempts to pull from sbd-agent, but the correct repository in the Red Hat Registry is storage-base-remediation-agent-rhel9.
2. Tag Mismatch: The operator defaults to the :latest tag. The official repository does not publish a latest tag; only specific version tags (e.g., v0.1.0) are available.

Steps to Reproduce:

1. Install SBD Operator v0.1.0.
2. Apply a default SBDConfig (do not specify spec.image).
3. Wait for the Operator to reconcile and create the DaemonSet.
4. Observe the image URL in the sbd-agent pods.

Expected Result: The default image path should point to a valid, pullable image (e.g., registry.redhat.io/workload-availability/storage-base-remediation-agent-rhel9:v0.1.0) so that the installation works out of the box.

Actual Result: The pods try to pull registry.redhat.io/workload-availability/sbd-agent:latest and fail with: failed to pull and unpack image ...: repository name not found to exist

Evidence: Pod events showing the failure on the default path:

Warning  Failed     ...  kubelet  Failed to pull image "registry.redhat.io/workload-availabilit