Error string propagation for global methods

Currently, the error string propagation works by calling `RegisterErrorMessage` on the base class whenever an exception is caught on the component side, which is then propagated to the binding and wrapped into a new exception.

This doesn't work for the global (`CWrapper`) methods, as there is no base class instance to register the error message on.

We ran into this issue as our "application" object is created and initialized using a global `CreateApp` method, which was throwing a `std::exception` due to missing runtime libraries. I would suggest to add the same mechanism to the `CWrapper` class so it too can propagate error messages.

首先跟踪基类中的 RegisterErrorMessage，以及 CWrapper 对 CreateApp 等全局方法的处理。确认组件侧如何捕获异常，以及 bindings 如何对其进行封装；当全局方法的异常能够像组件方法的异常一样，通过 bindings 传递其错误字符串时，这项工作就完成了。

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