Clarify special case of offset history update
Clarify special case of offset history update

If the current sequence has literal length of zero then an offset value
of three is handled in a special manner. While I implemented a golang
decoder I had to consult the educational decoder for clarification on
the update of the offset history in that case. This commit provides the
clarification that the offset value Repeated_Offset1-1 is handled as a
new offset is added to the offset history accordingly.

Cyan4973/zstd,Cyan4973/zstd,Cyan4973/zstd,Cyan4973/zstd,Cyan4973/zstd