Use proper contains/doesNotContain logic for car

The assertion for the car was always asserting that the app should be
blamed regardless of the trustVoiceService parameter. We have separate
logic for getting the description text between phone and car, but there
doesn't seem to be a need for separate assertion logic.

Bug: 205261586
Test: atest RecognitionServiceMicIndicatorTest
Change-Id: I356107be57c0594b73e6807b5c5a824e0731dcfe
1 file changed