Add slow test detection

[JesusTheHun]

Clear and concise description of the problem

The conclusion of #6534 is that slow test detection apply to any top level task within a file.
I use slow test to detect issues in a test design, so detecting a slow suite does not help me since tests can be added to a suite, leading to an increase in the overall time.

I understand that some people use that to make sure the test time is evenly distributed between shards ; that’s not my usage.

Suggested solution

Either a granularity option, or a new option to detect slow test only.

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[sheremet-va]

I don't understand the issue. The duration is reported for tests and suites. Don't look at a suite time if you don't need it

[JesusTheHun]

In the current state of things, slow top-level tasks are reported by highlighting the duration of the task. If a test duration is higher than the threshold, it is not highlighted.

I would like the same highlight at the test level.

[sheremet-va]

In the current state of things, slow top-level tasks are reported by highlighting the duration of the task. If a test duration is higher than the threshold, it is not highlighted.

It is a bug then, and not a feature request

[sheremet-va]

And I cannot reproduce it:

[github-actions]

Hello @JesusTheHun. Please provide a minimal reproduction using a GitHub repository or StackBlitz (you can also use examples). Issues marked with needs reproduction will be closed if they have no activity within 3 days.