Capture user logs from out-of-proc language async functions

If function code tries to log after function invocation completes, for example:
```
context.done()
context.log("func done");
```
Log "func done" is lost and host does not have an execution context to log to user logs

Start by tracing how the host handles out-of-process language-worker invocations and user logging after context.done() completes. Reproduce the example where context.log("func done") is called afterward, then verify that the message is retained in user logs despite the completed execution context.

Written by the indexing model from the issue text.