Report portal is not handling TestNG test method invocationCount correct.

[the-octopus]

Scenario: When run a test method more than one iteration by configuring the invocationCount property of the test method.
Correct behavior: the test method should appear in report portal as one level that has nested iterations.

Current behavior: each iteration from the same method appears as a standalone test method level.

for more details please check this [URL comment](#96 (comment))

[HardNorth]

That change requires server updates.

Classic retry looks like this: skipped->skipped->passed/failed.
It's counted as a single test in our statistics. It is marked as failed only if the last one in the retry chain is failed, when there is no attempts left.

InvocationCount looks like this: passed/failed->passed/failed->passed/failed
It should be counted as 3 tests. And if one of them failed the whole batch should be marked as failed.

Currently RP server supports only retries, not invocations. So invocations will stay as separate items until we implement such feature on the server side.

[HardNorth]

@evjlobanova Please include such feature in the future scope as we agreed.