ResidentWebRunner::attach calls ChromeTab::connect without providing an error handler, risking top-level errors without stack traces #153556
Description
From #153298 (comment) (shortened version):
Looking at this code I also noticed that ResidentWebRunner neglects to pass onError callback to ChromeTab.connect. This seems like an oversight...This callback is used as an onError callback on the WebSocket stream once connection is established. Not passing onError means that all exceptions which occur later (after connection was established and upgraded to WebSocket) are going to be uncaught and will crash Flutter tool as well.
Said another way, we should pass an error handler in this ChromeTab::connect call:
This error handler could simply rethrow the provided error using the provided stack trace using Error.throwWithStackTrace(error, stackTrace).