OMASA rateswitch to PARAM_ONE_OBJ uses invalid data for the first 2sf
### Basic info
- Commit SHA: c6ae2d8d26304d4c61bf1d8818fc4bec07046ce2 (main)
- Platform: all
### Bug description
When the bitrate switching in the decoder enters the OMASA mode `PARAM_ONE_OBJ` from another mode, the object metadata in `st_ivas->hMasaIsmData` is not zeroed and may contain old values. Since the reading and writing of this ringbuffer -like structure is done with an offset of 2 sub-frames the values read for the first 2 subframes are invalid. When staying in the mode, the ringbuffer content is valid.
### Ways to reproduce
(Clear steps or refer to a failing automated test, e.g. with a pipeline link)
<!--- Below are labels that will be added but are not shown in description. This is a template to help fill them.
Add further information to the first row and remove and add labels as necessary. -->
issue