Set up automated monitoring for slow jest specs
We recently started seeing some flakiness in jest jobs on master, probably happened after !149614 (merged) was merged.
The problem is that we see a high variance in execution time of certain specs, so it is hard to pin down what causes these specs to take so long. As a quick workaround, we bump the the max test exectution time: !150123 (merged)
We already have a jest speed reporter: https://gitlab.com/gitlab-org/frontend/playground/jest-speed-reporter. The plan would be to extend it to look at the latest X pipelines and identify jobs across pipelines.
Edited by Lukas 'ai-pi' Eipert