Aqua-agent Daemonset is broken since AKS uses containerd instead of Docker

Hi,

It seems since we have been updating the AKS version, this version is now using containerd instead of Docker.
The aqua-agent agent cannot start due to the following error:

Error:
`Cannot connect to the Docker daemon at unix://`

Aqua-agent is still expecting to use Docker, is there any fix for this ?

Start by reviewing the Aqua-agent DaemonSet configuration and how it assumes a Docker socket on AKS. Reproduce the reported startup failure on a containerd-based AKS version, then verify that the agent starts without the Docker daemon connection error.

Written by the indexing model from the issue text.