plugin timeout error on read fails to update plugin state to inactive

[edaniszewski]

With a local docker-compose deployment, killing the emulator plugin and hitting /read will result in an error for the plugin because the plugin is down. subsequently getting the plugin state, it is still marked as active. This is likely an issue with error handling/scope of the client context manager used to communicate with the plugin.