ISM rendering broken possibly due to object editing

While debugging the test case for sa4/audio/ivas-basop#2183 (closed) I noticed ugly modulation/buzziness artifacts for the FOA output that are gone when the -obj_edit NULL parameter is given to the decoder command-line. Because this test case involved frame error and JBM, I investigated it further and found that this a generic issue that is there for any rendering output_cofig, but not there for EXT output nor when -obj_edit NULL parameter is given.

An example configuration for the case (SHA : eb6212c5)

./IVAS_cod -ism 3 /scripts/testv/stvISM1.csv /scripts/testv/stvISM2.csv /scripts/testv/stvISM3.csv 384000 48 /scripts/testv/stv3ISM48s.wav stv3ISM48s.wav_3_ISM_with_metadata_at_384_kbps.192

decoding to binaural ./IVAS_dec binaural 48 stv3ISM48s.wav_3_ISM_with_metadata_at_384_kbps.192 .stv3ISM48s.wav_3_ISM_with_metadata_at_384_kbps.BINAURAL.wav

decoding to EXT

decoding to binaural with object editing enabled ./IVAS_dec -obj_edit NULL binaural 48 stv3ISM48s.wav_3_ISM_with_metadata_at_384_kbps.192 stv3ISM48s.wav_3_ISM_with_metadata_at_384_kbps_obj_edit.BINAURAL.wav

IMO this leads to some sort of bug in the handling of the metadata introduced from the object editing