[Reporting] Automated bisection to identify significant changes in performance

[mruberry]

This is an idea that @IvanYashchuk and I had, recording here so we don't forget. fyi @kiya00

Inspired by @kiya00's work on reporting tooling, we think it would be very interesting to have a function that could identify commits that caused significant performance changes. Maybe the function could take an fx graph or reproduction script and a range of dates or commit values and then bisect thunder to identify where performance significantly changed.

We should work out the details of this together.