Indigo/convert error appears in console after loading of corrupted MOL V3000

**Steps to Reproduce**
1. Open Canvas in Remote mode
2. Open from corrupted file (for example file with RDF sign):
[rdf-mol-v3000-no-reaction-3-elements.zip](https://github.com/user-attachments/files/16562046/rdf-mol-v3000-no-reaction-3-elements.zip)
3. Click on Add to Canvas

**Expected behavior**
Error is displayed, but no issues are in console in Remote mode

**Actual behavior**
Error is displayed and Indigo/convert error appears in console in Remote mode

**Environment details:**
- **Ketcher** [Version 2.24.0-rc.1] Build at 2024-08-06; 19:25:43
- **Indigo** Version 1.23.0-rc.1.0-g85f89b8f5-x86_64-linux-gnu-11.2.1
- OS: Windows 11 Enterprise
- Browser: Chrome, Version 127.0.6533.100 (Official Build) (64-bit)

**Additional context**
- Issue is detected during testing of Load RDF feature https://github.com/epam/Indigo/issues/2030, in scope of this feature we are adding only loading from RDF files based on RXN V2000, V3000

Start by reproducing the issue in Canvas Remote mode with rdf-mol-v3000-no-reaction-3-elements.zip, then follow the Add to Canvas path and the Indigo/convert error. Check how the corrupted MOL V3000/RDF input is handled. Done means the user-facing error remains displayed while no Indigo/convert error is written to the Remote mode console.

Written by the indexing model from the issue text.