mm-video: vidc: Fix frameparser behavior on EOS with data

The frameparser currently holds back any bytes that may be part of
the next frame's start code. In general, this results in frames
ending in 0x00 or 0x00,0x00 being marked as partial and properly
flushed on the next parse_sc_frame call. If an EOS is received
with data, this flush never occurs. In that case, this change
copies the missing bytes to the destination frame.
author: Leena Winterrowd <lenhardw@codeaurora.org>

Bug: 10668205

Change-Id: Ia7f1d795b2459da86f1bf6cdb5f8ca8e21c306bd