feat(events): configurable buffers and predicates

[jakubdyszkiewicz]

Checklist prior to review

This PR improves an event bus.

Until now, every event listener created a channel and whenever we send an event, we send it into a channel. This means that whenever there is a full channel we are stuck on .Send. The cause of this can be a single listener that is not reading fast enough.
I changed the event bus to drop the event in this case and emit a log. Additionally:

• I created a config for the channel buffer. If we see that listeners are not consuming events on time, we can always increase this buffer without releasing a new version of Kuma.
• I introduced predicates. For example, if there is a listener that only cares about a specific event we can define a predicate. This way we can avoid putting unnecessary events into a channel.

• Link to relevant issue as well as docs and UI issues --
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as a image registry) and it will work on Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS --
• Tests (Unit test, E2E tests, manual test on universal and k8s) --
• Do you need to update UPGRADE.md? --
• Does it need to be backported according to the backporting policy? (this GH action will add "backport" label based on these file globs, if you want to prevent it from adding the "backport" label use no-backport-autolabel label) --
• Do you need to explicitly set a > Changelog: entry here or add a ci/ label to run fewer/more tests?

[lahabana]

I think it might be better to not do the reconcile where we dequeue from the eventBus.