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.

Empieza rastreando RegisterErrorMessage en la clase base y el manejo de CWrapper para métodos globales como CreateApp. Confirma cómo se capturan las excepciones en el lado del componente y cómo las envuelven los bindings; el trabajo estará terminado cuando las excepciones de los métodos globales propaguen sus cadenas de error a través de los bindings igual que las excepciones de los métodos de los componentes.

Escrito por el modelo de indexación a partir del texto del issue.