Figure out how to properly support TLS with multiple processes

[grcevski]

We currently have one BPF program which we load when instrumenting with kprobes. The load of this BPF program checks if the executable we are instrumenting has loaded libssl and then instruments the library. In certain cases like nodejs, the runtime vendors libssl and we try to instrument the executable itself.

However, we load the BPF program once and whatever the initial configuration was we'll only instrument that. It's not a problem with the kprobes, because they are consistent across all executables, but we need special logic for instrumenting SSL.

Namely we can have the following scenario:

• Application without SSL is instrumented first.
• Application that dynamically links libSSL is loaded.
• Application that vendors libSSL is loaded.

We need state flag that we've instrumented libssl and then instrument if the executable requires it.
We need to always check if the executable vendors libssl when we find new non-Go executable.