lookupAndDeleteMapKeysValues function (tracer.go) now iterates the map and removes each read entry individually.

This could lead to a race condition (improbable, though) and we might loose few information. Newer versions of the kernel support other methods that could improve the process:

• LookupAndDelete (Kernel>=4.20)
• BatchLookupAndDelete (Kernel >= 5.6)

Detect at runtime whether these functions are available and use them when possible. (E.g. they should be available on rhel9 / ocp4.13+)

They could also greatly improve performances (this part LookupAndDeleteMap was identified as a bottleneck in user space profiling)