Gracefully fail setting up individual events

[AlonZivony]

As there are more and more reasons for an eBPF program to fail while loading,
it seems that a more flexible approach to a failure is needed - instead of exiting, tracee should log that it failed to load the event and move on.
This dynamic loading should be both for failure in the loading itself, or because of some missing dependency.
It is critical to unload/prevent the loading of eBPF programs which depends on failed one, and also unload/prevent the loading of programs which the failed one depends on would be beneficial (for reducing performance for unneeded programs).

Examples for failing reasons because of dependencies:

• Failed loading kernel symbols
• Failed loading critical kconfigs

[rafaeldtinoco]

Related: #1588