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 と、CreateApp などのグローバルメソッドに対する CWrapper の処理を追跡します。コンポーネント側で例外がどのように捕捉され、bindings によってラップされるかを確認します。グローバルメソッドの例外が、コンポーネントメソッドの例外と同様に、bindings を通じてエラー文字列を伝播するようになれば作業完了です。

索引モデルが issue の本文から書いたものです。