SELinux Profile Bindings don't seem to work

In the daemonset object, when the customer specifies the selinux profile explicitly using securityContext->seLinuxOptions->type, the profile gets assigned as [expected.]
If the customer removes that part, the customer thought that using a security profile binding would be sufficient in order to have the profile injected automatically (by the mutating webhook the cutsomer assume).
But when the customer checks the pod specs the selinux type is empty and the container context is set to the default container_t.

Start by tracing how the operator handles security profile bindings and whether a mutating webhook processes DaemonSet pods. Compare pod specs with and without securityContext->seLinuxOptions->type, then verify that the binding produces the intended SELinux type rather than the default container_t.

Written by the indexing model from the issue text.