When `pipeline(callback)` or `transaction(callback)` is called repeatedly
in a long-lived coroutine (e.g. while(true) loop), each call registers a
new `defer` closure via `__call()`, but the outer `executeMultiExec()`
finally block immediately clears the context connection. Since
`Context::has()` uses `isset()` which returns false for null values, the
next call sees no existing connection and registers yet another defer.

These defer closures accumulate indefinitely because the coroutine never
terminates, causing a slow memory leak.

Fix: Move the `Context::has()` check into the finally block so it
evaluates after `__call()` has stored the connection. This way the
connection stays in context and is reused on subsequent calls, with only
one defer ever registered per coroutine.

Made-with: Cursor

Made-with: Cursor

…e methods

Made-with: Cursor