[ DWDS ] Disconnect non-DDS clients when DDS connects (#2671)

The native VM service disconnects all non-DDS clients when DDS connects
in order to keep state consistent. DWDS was never configured to work
this way and, instead, would not let DDS connect if there were already
existing clients.

This is fine most of the time, as DDS is typically the first client, but
in cases where multiple DDS instances attempt to start at once (e.g., a
simultaneous `flutter run` and `flutter attach`), this inconsistency
prevents tools from falling back to using an already connected DDS
instance, as seen in flutter/flutter#171758.

Fixes #2399

Author: bkonyi

dwds/CHANGELOG.md

@@ -1,3 +1,10 @@
+## 25.0.2
+
+### Bug Fixes:
+
+- Fix issue where DDS would fail to initialize if DWDS already had existing
+  clients.
+
 ## 25.0.1
 
 ### Bug Fixes:
@@ -73,6 +80,7 @@
   libraries instead of assuming it exists in the global `window`.
 
 ## 24.3.5
+
 - Allow clients to specify the `packageConfigPath` in `LoadStrategy` class and associated providers.
 
 ## 24.3.4
@@ -157,7 +165,7 @@
 
 ## 23.1.1
 
-- Loosen `package:vm_service` constraints to allow `>=13.0.0 <15.0.0`.  - [#2329](https://github.com/dart-lang/webdev/pull/2329)
+- Loosen `package:vm_service` constraints to allow `>=13.0.0 <15.0.0`. - [#2329](https://github.com/dart-lang/webdev/pull/2329)
 
 ## 23.1.0