Improve Tracer performance, reduce CPU consumption at the scanning stage

[alongir]

Current:

• When Tracer starts running it consumes a significant amount of CPU, probably related to the number of processes running on the node as it inspects all processes to find TLS elements (e.g. libraries and GOlang programs)
• The high consumption continues until all processes are inspected.
• This elevated consumption can cause OOMKilled for the Worker pod.
• On OOMKIlled this process begins again.
• While this happens on busy nodes and can be resolved with more resources, we can likely improve this behavior

Requested:

• Throttle the scanning process
• Enable/disable detection of TLS elements (e.g OpenSSL, Golang programs, etc) - this is optional and great for debugging. Yet if you solve the throttling, this feature gains a secondary priority.