Currently the flutter tool knows how to talk to the vm_service in 3 separate ways.

1. The vm_service_lib which is still pulled in transitively from package:coverage. (@grouma has expressed plans to upgrade this package to use the modern vm_service_client).

2. The vm_service_client, which might only be used transitively, but contains the fully generated API.

3. Our own vm_service client implementation. This does not cover the full API, only the parts require for hot reload.

We should identify the feasibility of replacing our implementation with the generated version.