[ProjectTracking]: automate detection of nayduck breakages

[marcelo-gonzalez]

Goals

Reduced time and effort needed to find the root causes of nayduck test failures, and hopefully fewer failures over time as a result.

Estimated effort

This would be taken by the node team, and might take a couple weeks

Currently nayduck failures are simply reported, and it's up to someone from the node team to investigate them and either fix them or make a reasonable effort to guess who might best be asked to look into it. This can be quite time consuming, and the effort needed can pile up, leading to a bad state of the nayduck test suite in general. One way to improve this might be to implement a feature in nayduck that will detect new failures and automatically re-run the test many times via git-bisect, hopefully finding the culprit. Then something we could consider is to have nayduck automatically generate a message tagging the breaking commit's author (maybe via zulip or email)