This task has multiple parts:

1. Move Kube-Enricher to a pipeline-oriented architecture so the parts have a clearer separation. There is already a PoC here: https://github.com/netobserv/goflow2-kube-enricher/pull/25
   1. Flowlogs2metrics already is implemented in the form of pipeline, where the pipeline manager invokes explicitly all the processing steps, but we might want to use a channel-oriented pipeline like the one in the PR linked above because (1) it's simpler to parallelise and implement asynchronously (2) it's simpler to configure e.g. via a configuration DSL.
2. Merge Kube-Enricher and Flowlows2metrics: Choose those Flowlogs2metrics parts that implement its functionality and integrate them into the Kube-Enricher pipeline. Also, replace those components from Kube-Enricher pipeline that could be already implemented in a better way in Flowlogs2metrics

Related document about the pipeline: https://docs.google.com/document/d/1SGI1X-4I9XBkOfpPMSPGMY1ScmyHBo5EdMsq0Q_nQQc/edit

Document from Joel https://docs.google.com/document/d/1OTiuYPHoZGyvp6MvBlTvgWUo99lZ2tgynhwe2voM0EM/edit#