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.

Start by tracing RegisterErrorMessage on the base class and the CWrapper handling for global methods such as CreateApp. Confirm how exceptions are caught on the component side and wrapped by the bindings; the work is done when global-method exceptions propagate their error strings through the bindings like component-method exceptions.

Written by the indexing model from the issue text.