Create a possibility to "replay" an output.xml (fast/realtime) with rebot and ListenerAPI there

There are listeners out there in the field that needs to be attached to a running robot and then posts results.

There are two use-cases for that:

1. Development of listeners (at least "read-only" listeners)
2. using reporting Listeners that can be run on output.xml
   a. (optionally) in realtime, if the listener is depending on the current time
   b. in fasts mode without any consideration of timings.

Examples:

### Allure
One example is the Allure report.
it has a listener that needs to run with the robot run.
It would be cool to just let that run with rebot --listener robotframework-allure output.xml
So it would not be needed during exec.

Failures in Listeners

There could be a situation that a listener fails and you do not understand why, so you want to debug it, but that error only happens after 2h of running robot. So running again on the existing output.xml would be good for debugging, and after fixing, you could actually still use these results to publish (with the now working listener)

Listener Development

When you develop a listener you run robot tests multiple times, but again with bigger ones ore non deterministic runs, it is hard to test your listener. a "rerun" option would be cool for that as well.

Cheers
René

Start by reviewing the rebot command and ListenerAPI, focusing on how output.xml is currently processed and how listeners attach during a Robot run. Define the expected fast and realtime replay behavior, including listener failures and reporting use cases. Done should mean the requested replay workflow is specified and validated for these cases.