BouncyBall: Consider NORMAL frame rate for testing

When we figure out what frame rate we're going to need from the
system at a minimum for the test, we now also consider
Display.FRAME_RATE_CATEGORY_NORMAL.

It's possible, when running in a large test suite, that the device
gets into a heated state from previous tests, and launches our app
below this NORMAL frame rate due to thermal considerations.  Rather
than test at this lower frame rate, we want to make sure we're
testing what the user would typically get as the frame rate.

Bug: 442631412
Test: Ran on a couple devices, although neither triggered the new logging statement
Flag: EXEMPT TEST_ONLY
Change-Id: I422afca5d1f21b5ffe02528eb63d34915a1de5f2