Better coroutine error handling

[fraidev]

This PR resolves #39

I added class CoroutineUtils.cs that has two methods:

• Try: Just run a coroutine with an optional handler for the exception (default is just a log).
• TryWith: Execute the Try method for a specific monoBehaviour.

[k-karuna]

In my opinion this solution is good, but didn't cover all cases. For example, in case of http issues we will receive exception on this line and this exception will be handled by existing CoroutineWrapper class.
So, my suggestion is maybe it will be better to improve CoroutineWrapper class that we can set up errorHandler action on it, and execute it instead of current Completed?.Invoke(default);
And when we wrap with it all coroutines that runs external callbacks and returns through yield return coroutine statement, looks like we will cover all possible exception cases.
Moreover looks like that WrappedRequest method is redundant, we can use ordinary CoroutineWrapper instead.
If you have any thoughts, feel free to write me.

[fraidev]

In my opinion this solution is good, but didn't cover all cases. For example, in case of http issues we will receive exception on this line and this exception will be handled by existing CoroutineWrapper class. So, my suggestion is maybe it will be better to improve CoroutineWrapper class that we can set up errorHandler action on it, and execute it instead of current Completed?.Invoke(default); And when we wrap with it all coroutines that runs external callbacks and returns through yield return coroutine statement, looks like we will cover all possible exception cases. Moreover looks like that WrappedRequest method is redundant, we can use ordinary CoroutineWrapper instead. If you have any thoughts, feel free to write me.

I really forgot about the CoroutineWrapper and WrappedRequest usages.
And CoroutineWrapper it was doing a similar job that the new CoroutineUtils.
What do you think to use the CoroutineUtils.Try in the WrappedRequest method and delete CoroutineWrapper because there is no more usage in the codebase?

[k-karuna]

This solution did not cover scenarios which are build on several yield return IEnumerator cases. E.g. if we click on Inventory button on UI, we will call this method, that will call GetJson<T> method later, and if we have some network issues, we will get deserealize exception on this line, even if we pass errorHandler on CoroutineUtils.TryWith
So, my previous suggestion was to use something like CoroutineWrappper, that can handle Exceptions inside itself and use them wherever possible.

[k-karuna]

@fraidev what do you think?

[fraidev]

@fraidev what do you think?

Make sense! I reverted the last commits and added one using the CoroutineWrapper with error handling.
Can you check again?

[m-kus]

@fraidev could you please update the changelog?

[k-karuna]

@m-kus @fraidev I've updated changelog in order not to delay this task.