[SUREFIRE-2065] Fix parameterized JUnit4 test reporting

[andpab]

This is an adjusted PR based on #516 from chalmagr.

I kept the additional ITs exactly as written by chalmagr.
The fix itself is different. It's less invasive, doesn't require making changes to the expectations of any expecting tests or ITs.

The root cause of the bug is that the logic for determining hasParams only looks at methodSource.getMethodParameterTypes(). That's not correct for JUnit 4 Parameterized tests since they do not have a method parameter. In JUnit 4 the parameterization is handled on a level further up.

The fix corrects the logic for determining hasParams so that it also works for JUnit4. It relies on the fact that for JUnit 4 parameterized tests there is a container-type test identifier with the legacyReportingName [<index>] or [<displayName>] that has an empty source field in the test identifier hierarchy - between the test method and the test class.

---

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.

[jbonofre]

I'm reviewing and testing the PR. Thanks.

[jbonofre]

LGTM, I'm just testing with junit5-vintage-engine to be sure it behaves well too.

[jbonofre]

@olamy ^^ can you please take a look and eventually merge ? A new surefire-plugin release would be great as well, I can prepare it if you want.