Removal of wasp-agent DaemonSet leaves the OCI hook in place, enabled unlimited swap for arbitrary burstable QoS class pods

[enp0s3]

Consider a scenario where wasp-agent is non functional, or was removed for some reason.
The OCI hook is still there to enable unlimited swap. Possible mitigation could be:

• Deprecate the OCI hook (enabling swap becomes racfeful, workload is started with swap disabled)
• Update the OCI hook to do health-check for its local wasp-agent pod
• Update the OCI hook to set the limited swap in the first place