IssueTracker

Currently, there are several problems with the architecture of BenchmarkState/BenchmarkRule:

• BenchmarkState has extremely complex state management due to attempting to expose a single keepRunning API
• Trace capture happens within BenchmarkRule instead of measureRepeated (to allow it to support the Java API)
• Yielding the main thread from within measureRepeatedOnMainThread() is awkward, and happens within the measurement loop
• sleep after thermal throttling is detected doesn't yield, so can cause ANRs with measureRepeatedOnMainThread (b/311242861)
• configuration (e.g. profiler, metric type, looping behavior) and data output (json, instrumentation results, traces) are distributed, and not easily simplified (ideally measureRepeated would return all of this data)

This bug tracks an effort to rewrite much of the top level control flow of BenchmarkRule / BenchmarkState to be based on coroutines, and address all the above problems.