…ce.enable has completed
I noticed in the logs that we can call functions before `device.enable` completes. It's a long shot, but I wonder if it might be what leads to the timeouts in #5793. We've had issues in the past where sending requests too early would cause issues, which lead to the `daemonStarted` promise, however it only awaited for _any_ output message and not for `device.enable` to complete.
This adds a new completer for `device.enable` completing, and then an additional 2s delay. If the timeouts reduce with this change, it might help narrow down the ultimate cause in the `flutter` tool.

DanTup added a commit that referenced this pull request

Some tweaks from review on #5948 from after it merged.

Open