Container-tracer does not work in nested namespaces

[tzstoyanov]

Describe the bug

In a nested namespaces environment, such as Kind clusters, the discovering the PIDs of the containers tasks fails. In that case, the Kubernetes API returns the PIDs as they are seen be the parent namespace. In order to attach a trace-hook, container-tracer needs the real PIDs, as they are seen in the root namespace.

Reproduction steps

1. Install container-tracer in a Kind cluster.
2. Configure and start a new trace session
3. Check the PIDs, on which the trace-session is configured - these are not valid PIDs in the root PID namespace.
   ...

Expected behavior

Container-tracer to work in a nested namespace environments, such as Kind clusters

Additional context

No response