Timestamps in JBM trace not affected by delay compensation

Initial samples from the decoder API are not written to the output wav file by the decoder app to compensate for processing delay. This is not reflected by trace file writing, causing timestamps in the trace files to be too late by the decoder delay amount with respect to the written audio file.

Example:

./IVAS_cod -stereo 48000 16 \
    ./scripts/testv/stvST16n.wav \
    stereo.g192
./scripts/tools/Darwin/networkSimulator_g192 \
    ./scripts/dly_error_profiles/dly_error_profile_5.dat \
    stereo.g192 \
    stereo.rtpg192 \
    stereo.netsimtrace \
    2 0
./IVAS_dec \
    -Tracefile stereo.jbmtrace \
    -VOIP STEREO 16 \
    stereo.rtpg192 \
    stereo.wav

Decoder prints:

------ Running the decoder ------

Frames processed:       1114

Decoder+renderer delay: 3.25 ms   ( 52 samples at timescale 16000)

Decoding of 1114 frames finished

Scaled regions in the output audio file begin and end 52 samples earlier than reported by the trace file.