Fix infinite draw loop

Both Chip and NavBarPill were sharing the same Drawable instance, but
rendering them in different sizes.

This caused setBounds() to be called twice with different values, forcing
the drawable callback to invoke invalidateSelf() at every frame.

Bug: 424295289
Fixes: 424295289
Test: perfetto trace
Test: atest AmbientCueViewModelTest
Test: atest AmbientCueInteractorTest
Test: atest FilterUtilsTest
Flag: EXEMPT bugfix
Change-Id: I97ad8b1a6849e2428f3547db25b69c6e73f38762