Tracking flaky tests over time and driving the process towards fixing them.

[javiercn]

We used to have a tool that enabled us to see what tests were flaky in the product, get quick access to the failures and drive the investigation and fix process. This broke due to quota limits on the resources we were using. This issue tracks bringing that tracking in some shape or form for team members to use.

[dougbu]

Suggest this is actionable as PRs to https://runfo.azurewebsites.net/. @jaredpar where are the sources❔ Or, is there a planned move into, say, https://github.com/dotnet/arcade-services ❔

Also, including this in the DoI project for discussion in that context.