Investigate whether it's possible to make PathResolver more resilient to long paths

Podman / overlayfs:

```
{"event_type":"FILE_RENAME","pids": ...,"old_path":"./test","new_path":"./test2"}
```

```
mv-170700 [003] d... 9717.441932: bpf_trace_printk: path truncated
mv-170700 [003] d... 9717.441938: bpf_trace_printk: path truncated
```

Check if the bottleneck is `PATH_RESOLVER_MAX_COMPONENTS` or `PATH_MAX` and if it makes sense to allocate more space; evaluate how often this happen