bug: Async exception handlers for activities are registered for containers

[jshook]

The activity exception handlers which are installed on behalf of thread pools should be associated with the activities first, and then any exceptions which are uncaught should be bubbled to the container.

Some error patterns seem to show an error for one activity being attributed to one after due to asynchrony between container commands without some barrier or explicit routing of errors through the correct error handler.

This part of the container and activity executor code needs to be audited and corrected to force commands to be fully processed serially within the container, including all error conditions.

Ideally, a future version of this would be based on structured concurrency.