[SUREFIRE-1709] Fire events when Provider execution is started and finished

**[Tibor Digana](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tibor17)** opened **[SUREFIRE-1709](https://issues.apache.org/jira/browse/SUREFIRE-1709?redirect=false)** and commented

Currently the XML reporter creates the report for a normal run. Then the same XML is written again by every rerun. This is not efective job.
Employing events specifying the begin and the end of the entire run would prevent from this happening.
If the rerun is not configured, the report can be created by test set completed as it is now.
If the rerun is configured, the reports should be produced at the end of the provider execution.

---

**Issue Links:**
- [SUREFIRE-1708](https://issues.apache.org/jira/browse/SUREFIRE-1708) skipAfterFailureCount should be coherent across multiple fork JVMs
(_**"Dependent"**_)
- [SUREFIRE-1710](https://issues.apache.org/jira/browse/SUREFIRE-1710) skipAfterFailureCount in JUnit5 provider
(_**"Dependent"**_)

Trace the XML reporter and provider execution entry points described in the issue, focusing on when reports are written during normal runs and reruns. Compare test-set completion with the beginning and end of provider execution, and inspect the dependent skipAfterFailureCount issues for related event behavior. Done means rerun reports are produced once at provider completion while non-rerun behavior remains unchanged.

Written by the indexing model from the issue text.