Core: Bound legacy savestate LZO decompression

Core: Bound FIFO memory updates

VideoCommon: error if the same asset id is used with a different type

Legacy savestate headers controlled both the compressed input length
and the decompression buffer size. The input was read into a fixed-size
buffer without validation, and the unsafe LZO API could write past its
output buffer.

Use the legacy block size as the output capacity, reject oversized
compressed blocks, and use the bounds-checking LZO decompressor.

FIFO logs control each memory update address and data size. Playback
masked only the start address into RAM or EXRAM, then copied the
complete update contiguously. An update reaching the end of a mapped
region could therefore write beyond host-mapped emulated memory.

Resolve the target through MemoryManager and reject updates larger than
the remaining valid span before copying them.

Android: Use TitleDatabase for game list

AMMediaboard: Update closesocket error code approriately