Readiness probes fail in RHOCP 4 pods after Twistlock pod is restarted or deleted

Issue

• readiness/liveness probes for Openshift pods fail with the following error:
  level=error msg="exec failed: unable to start container process: error starting setns process: fork/exec /proc/self/exe: no such file or directory"
• DNS resolution problems on application pods for /etc/resolv.conf file missing in the pod.
• The application pod does not have the /var/lib/containers/storage/overlay/<id>/merged/ directory.