Bug#39033858 Parallel_reader::Scan_ctx::copy_row copies wrong range of bytes

Problem:

InnoDB uses a convention where rec pointers point in between two
fragments of the record: to the left of it, are so called "extra"
bytes which contain metadata such as flags, info about which fields are
null and what is their length. To the right of it, is the actual data of
the fields.
The function rec_offs_size(offsets) returns the total length of the
record which is the sum of these two:

rec_offs_data_size(offsets) + rec_offs_extra_size(offsets)

The logic of Parallel_reader::Scan_ctx::copy_row() copied that many
bytes into a freshly allocated buffer, but used rec address as the
source, instead of "rec - extra", resulting in copying wrong range of
bytes.

Solution:

Adjust the logic to copy the correct range of bytes.

Change-Id: Ia0463e4a752dfce70ff5a2ac83818132de9a638c

Commit
https://github.com/Wen-He/TXSQL/commit/52de0a885eb1bbfdaa1f03f5352419a124c8f419

Upstream Reference
https://github.com/mysql/mysql-server/commit/c4148fad113945e51b1a44e88a798e87216a7c3b

まず Parallel_reader::Scan_ctx::copy_row() を見つけ、rec_offs_size(offsets)、rec_offs_data_size(offsets)、rec_offs_extra_size(offsets) がコピーする範囲をどのように決定するかを調べます。ロジックを、issue で参照されている upstream MySQL commit と比較します。完了条件は、buffer が正しいソース範囲から完全なレコードを受け取ることです。