Failing to run when loading an incompatible plugin

In the VM, we have an instruction to load plugins (.dll, .so and .dynlib, depending on the OS), working perfectly when Ark *and* the plugin have been compiled with the same compiler *and* the same compilation options (both debug or both release).

A problem occurs when we use a debug plugin with a release ark: ark silently fails to load it, throwing an exception we aren't catching / interpreting as "bad plugin".

This should be investigated to be able to tell the user that the plugin couldn't be loaded, and we should abort execution (no plugin loaded => undefined symbols later on, coming from the plugin we didn't load, thus can not execute: better to abort to give a clear error message).

This problem will mostly be encountered by our contributors and development team, as our end users are only being provided the final binaries, which we should test before publishing. When developing we sometimes forget to recompile everything, and it's really annoying because we start searching for a bug in the VM while it's just a target to recompile.

从实现加载 .dll、.so 和 .dynlib 插件指令的 VM 代码开始。使用 release Ark 重现加载 debug 插件的情况，然后跟踪未捕获的异常并定义失败路径，使不兼容的插件产生明确的错误并中止执行，而不是将未定义的符号留到后续处理。

由索引模型根据 Issue 内容生成。