Decouple ROFL event notifier and sub-handler

[peternose]

The ROFL event notifier should be decoupled from the ROFL sub-handler to ensure that these structures are independent of each other. Additionally, the ROFL event notifier should terminate when the ROFL component is stopped (e.g., during an upgrade) to prevent resource leaks.

Ideally, every RONL component should have a handler and a notifier, and every ROFL component should have a sub-handler and a sub-notifier.

[kostko]

This is also causing problems with notifications not being delivered to components in case there are multiple components and some are not working. The reason is sequential call propagation with a shared context. When we have sub-notifiers, this somewhat hacky call propagation can be removed.