Splitting latency tracker test into two test classes

DisplaySwitchLatencyTrackerTest was covering a lot of cases also implicitly testing FoldableDisplaySwitchTrackingInteractor. But that made tests and setup pretty complex so this CL is creating separate test for FoldableDisplaySwitchTrackingInteractor and leaving in DisplaySwitchLatencyTrackerTest only tests related to that class functionality.

Also that required injecting interface instead of class into DisplaySwitchLatencyTracker to provide easy to use fake. That in turn triggered several drive-by dagger changes.

Bug: 405128401
Flag: EXEMPT mostly test refactoring
Test: DisplaySwitchLatencyTrackerTest, FoldableDisplaySwitchTrackingInteractorTest
Change-Id: I0f832be0ae4859db85477be7ce70600aced23f96