lib/lzo: Do not leak implementation details in lzo1x_1_compress()

The previous compressor version could produce slightly different (but
of course valid) compressed data representations, depending on
implementation details like CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS.

Avoid that by synchronizing (partial unrolling) all affected code paths.

This update also allows backing out the previous testvector input change.

Signed-off-by: Markus F.X.J. Oberhumer <markus@oberhumer.com>