[SUREFIRE-2015] Implement testRunId and RunMode in the SimpleReportEntry

[Tibor17]

This PR is the most important because it implements RunMode and testRunId in the ReportEntry, TestSetReportEntry, SimpleReportEntry, CategorizedReportEntry and WrappedReportEntry in appropriate implementation form.

Additionally, I had to distinguish between two events (OutputReportEntry, TestOutputReportEntry) and therefore the interface TestReportListener handles them via generics dependeing on the situation.
The first situation happens when provider's listeners handles the event OutputReportEntry from System.out and System.err via the ConsoleOutputCapture. The ConsoleOutputCapture does not have any notion about runMode and testRunId, and therefore the only provider's listener would add runMode and testRunId to a recreated entry which would be finally propagated to the ForkingRunListener and TestSetRunListener. The runMode and testRunId are determined opon the events testStarted and any test end and Thread local.
The second situation happens when ForkingRunListener and TestSetRunListener handles TestOutputReportEntry which contains runMode and testRunId.

Some classes are deprecated in the module surefire-junit47 and can be freely removed after the XML Reporter would be fully capable of parallel tests (must support events chaos in one thread). That's the reason why parallel tests are badly handled in JUnit5 reports. The provider surefire-junit47 also supports parallel tests and we do not see the problem with undeterministic XML report, but the reason is that the provider has a cache, eats the memory including the std/out logs and all the messages and test events are replayed in a sequence as if the tests were executed in one thread.

Following this checklist to help us incorporate your
contribution quickly and easily:

• Make sure there is a JIRA issue filed
  for the change (usually before you start working on it). Trivial changes like typos do not
  require a JIRA issue. Your pull request should address just this issue, without
  pulling in other changes.
• Each commit in the pull request should have a meaningful subject line and body.
• Format the pull request title like [SUREFIRE-XXX] - Fixes bug in ApproximateQuantiles,
  where you replace SUREFIRE-XXX with the appropriate JIRA issue. Best practice
  is to use the JIRA issue title in the pull request title and in the first line of the
  commit message.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Run mvn clean install to make sure basic checks pass. A more thorough check will
  be performed on your pull request automatically.
• You have run the integration tests successfully (mvn -Prun-its clean install).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

• In any other case, please file an Apache Individual Contributor License Agreement.

[Tibor17]

@slachiewicz
Now only SUREFIRE-2014 remains to complete the entire SUREFIRE-1860.

[Tibor17]

@slachiewicz
If a Javadoc is missing somewhere, I can add one of course.

[slachiewicz]

@slawekjaranowski ?

[Tibor17]

@slachiewicz
Sorry for typo. My bad!
May I ask you for having a look since you are already here? Thx

[slawekjaranowski]

please add javadocs for new interface/ classes 😄

[slawekjaranowski]

private field runMode can be removed

[Tibor17]

Thx, done :-)

[Tibor17]

The RunMode will be finally removed in AbstractStandardStreamEvent and EventChannelEncoder in the SUREFIRE-2014.

[Tibor17]

@slawekjaranowski Javadoc was added.