refactor: Dynamic memory import.

[Zurcusa]

Description

Switch to dynamically loading the memory import from the provided wasm files. Also removes the manual parsing logic for the custom sections.

• What does this PR do? Loads the memory import dynamically from the provided runtime wasm. Further Improves the custom section parsing.

• Why are these changes needed? Defining a static memory import causes runtime init failure when the runtimes change their minimum memory limits.

• How were these changes implemented and what do they affect? They're implemented with the help of this parser.. The memory import is extracted before the initialization of the runtime instance and loaded in its imports.

Fixes #445

Checklist:

• [x] I have read the contributing guidelines.
• [x] My PR title matches the Conventional Commits spec.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.

[David-Petrov]

I see the WasmCustomSection record previously used as a DTO for the API of WasmSectionUtils is no longer used. If you deem that the newly imported dependency chicory renders the old API obsolete, then I'd also remove WasmCustomSection. Seems to me that this is the case.

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud