text: Title: Listeners are not notified about actions they initiate
  Body: If a listener runs a keyword using `BuiltIn.run_keyword` or logs a message using `robot.api.logger`, their `start/end_keyword` or `log_message` methods are not called. This is inconsistent, because if listeners modify the data so that they add new keyword calls, their `start/end_keyword` methods are called and, if keywords log something. also `log_message` is called. This also leads to a situation where the result model will have more information that listeners have received. I noticed this when enhancing the result model created during execution so that it contains also log messages (#5260). 
  
  The reason that listeners don't get notifications from actions they initiate is that it is explicitly prohibited to avoid recursion. Recursion is a valid concern, because if `start_keyword` blindly calls `BuiltIn.run_keyword` or `log_message` blindly calls `logger.info`, they end up being called again until the recursion limit is exceeded. That is, however, a bug in a listener and it should be fixed. The change is nevertheless backwards incompatible, because buggy listeners won't work anymore.