Resolve "Timestamps in JBM trace not affected by delay compensation"

• Related issues: #1361 (closed)
• Requested reviewers: @tamarapu

Reason why this change is needed

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.

Description of the change

• To keep timestamps in sync, the decoder now throws an error if -Tracefile is given on the command line without -no_delay_cmp. See issue page #1361 (closed) for details.

Affected operating points

• Decoder in VoIP mode when JBM trace file writing is enabled: BE apart from the requirement for delay compensation to be disabled.

Related to #1361 (closed)