FrameDecoder: modify mSource->stop timing

1.In abnormal situations, due to the queueInputbuffer is interrupted when the first frame is input, and it returns and exits directly.
2.At this time, the FrameDecoder objec is handled by the AsyncLooper.
3.The old FrameDecoder object is nit destroyed in time to stop mSource.
4.A new FrameDecoder object is created directly and mSource is started repeatedly.
Therefore, when the input thread exits due to err, it actively calls mSource->stop

BUG: 416406851
Test: run cts -m CtsMediaMiscTestCases
(cherry picked from https://partner-android-review.googlesource.com/q/commit:c04cd6c60b519e311270e76f6682a0a776fb6a7f)
Merged-In: I2dbba1dd46372e7077e5e95f02be90938dc066fc
Change-Id: I2dbba1dd46372e7077e5e95f02be90938dc066fc
Flag: EXEMPT bugfix