Basop 2500 renderer configuration range check refactoring

• Related issues: #2500 (closed)
• Related float MR: ivas-codec-pc/ivas-codec!2599 (merged)
• Requested reviewers: @szczerba

Reason why this change is needed

• The range check of the renderer configuration is not fully implemented in BASOP. However, it needs to be done before the conversion to fixed point values. This creates a difference to the floating point code, where the check is done after the values have been imported to the renderer configuration struct.

Description of the change

• Move the range check such that it is done on the RenderConfigReader handle instead of the RenderConfig handle. This way the checks can be done the same way in float and BASOP, and it ensures the values are within range when converting to fixed point.

Affected operating points

• Affects binaural reverb renderer configuration, where the configuration values are out of range.
• Should be BE for all tests, since no test uses values out of range.