MASA part rendering of OMASA does not always follow correct path in internal renderer
### Basic info - Commit SHA: a2c05c47330c27eb3d69b0419477294bd1fcbaa9 - Platform: all ### Bug description First noticed when fixing stereo type detection in MR !2595. It seems that MASA stereo type detection initialization has been missing a long time a condition for OMASA which leads to activation of the correct code path for the MASA part only when the format is signaled as MASA (which is at 24.4 kbps). This causes similar collapse of spatiality for MASA part when output is to Ambisonics as was fixed by MR !2595. Also rate switching suffers from this as stereo type detection is initialized and uninitialized more often than required. Notably, external renderer does not have this problem as there the combined formats are separately rendered. ### Ways to reproduce Any OMASA bitstream at 32 kbps or above and output is Ambisonics. <!--- 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