[FEAT] Janitor Events Consumer Interface

[NDStrahilevitz]

Prerequisites

• [x] This issue is an EPIC issue (add label: EPIC).
• [ ] This issue is an EPIC TASK (add issue to EPIC description).

Select one OR another:

• [ ] I'll create a PR to implement this feature (assign to yourself).
• [ ] Someone else should implement this (describe it well).

Feature description

Many features in tracee use the existing events and consume them as sources of info for later use in enrichment or configuration changes. Existing examples in the code currently are the the Containers and ProcInfo structs. We should formalize this concept for future use in similar features for example:

1. Network interfaces being attached and detached responding to events
2. Devices being added
3. CPU and memory growth and reduction, tuning parameters
4. Probes responding to events (for example new containers could make tcProbes attach to them)

In addition, we could add new event sources that track the OS to create these janitor events into the pipeline.

@rafaeldtinoco

Additional Information (feature drawings, files, logs, etc)

[rafaeldtinoco]

@NDStrahilevitz I believe this case is not directly related to #1922, but if we decide to go with a side channel for janitor events, then it could be related.

[NDStrahilevitz]

I think this was more for general system monitoring which doesn't come from eBPF. But most of it could come. For the moment #1931 can suffice so i'll mention it here.

[yanivagman]

Closing in favor of #3086