Refactoring/retry model

[mreiche]

Description

Completly refactored test status model.

• Improved statistics for statuses
• The Retried status doesn't count as failed anymore
• Fixed related/depend methods for retried methods
• Added new status Repaired
• Relabeld PASSED_RETRY to Recovered and FAILED_RETRIED to Retried
• Fixes Refactor RETRY statuses #141
• This PR requires teamcity-connector update as well Fixed teamcity statuses testerra-teamcity-connector#3

Retried tests are no longer part of the statistic:

More detailed information on the status badge:

Links between retried methods:

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[martingrossmann]

After some changes this is the latest version of the dashboard after executing the class TestNgDependsOnRetryTest:

• The retried test is part of the executed tests (5 tests) but it has no impact to the whole test result. This is passed
• The failure aspect comes from the retried test.
• The dashboard filter for Failed ignores the retried test. This test is only available in the Tests area.

@gogro @mbeuthan Please review. :-)