Allow uncaught exceptions to "trigger" another function for global exception handling

Both related to this request

https://feedback.azure.com/admin/v3/suggestions/20308660/

And the fact that people today using bindings aren't able to catch an exception from something like an output binding in the context of the language worker.

Start with the linked Azure feedback suggestion and the issue description of output-binding failures in language workers. Investigate the host's current handling of uncaught exceptions and binding errors, then clarify the design and acceptance criteria for triggering another function for global exception handling.

Written by the indexing model from the issue text.