Vector files capture might use incorrect offsets

[AlonZivony]

Description

In the code of the send_bin_helper function, I noticed that we add to the start offset of the chunk when reading io_vector the full size of the last vector written:

        bin_args->start_off += bin_args->full_size;

However, we also add to this offset while writing (except for the last chunk):

        bin_args->start_off += F_CHUNK_SIZE;

So, if I am not mistaken, the start offset of the next vector node will be 2*full_size - last_chunk_size.
We use this offset as the offset for the output file, so it will fill many blank areas in the output file between each vector node.

I haven't tested it yet on captures, only noticed it in the code.

Output of tracee version:

(paste your output here)

Output of uname -a:

(paste your output here)

Additional details