Fix unsecured asynchronous execution of coroutines with GDRx-Try-Catch

[Neroware]

The ErrorHandler is not asynchronous meaning it breaks when a coroutine is used within a GDRx-Try-Catch-object. I recommend using a disposable to maintain information on the current error-handling frame, which is inserted into the risky function like this:

GDRx.try(func(frame) ... await foo ...).catch("Error", func(e): ...).end_try_catch()

This should make it possible to keep information on the handled errors for as long as the coroutine is running.

[Neroware]

Welp, I think this actually might be technically impossible using only GDScript. We cannot get any information on the current call stack and the currently running callable in control flow. (I know, there are methods that print stack info, but these are only for debugging). Suggestions would be welcome, otherwise I do not know if this is not impossible...