Fix failing/flaky TextViewActivityTests

These tests are flaky because each negative assertion in Espresso
is taking about a minute or two to run. Espresso is waiting that long.

This cl solves the issue by:
1. Deprecating and excluding the negative assertions where they are
   not required for the test to still be meaningful.
2. Re-written to no use negative assertions where possible.
3. Suppress a failing test. We're not getting much value from this
   anyway.
TODO (in incoming cl):  Alternative action mode assertions.

Change-Id: Ic808f687151d225689d839b4caf4ef0b8d70cff0
Bug: 67023680
Test: bit FrameworksCoreTests:android.widget.TextViewActivityTest