Support running DWDS without a Chrome Debug Port (web-socket-based)

[jyameo]

• Implemented a WebSocket-based communication protocol that provides essential developer tooling (hot reload, service extensions) when Chrome debugger access is unavailable. - #2605
• Added WebSocket-based hot reload and service extension support via new WebSocketProxyService class that implements VM service protocol over WebSockets.
• Created new files: WebSocketProxyService, WebSocketDebugService, WebSocketAppDebugServices, and WebSocketDwdsVmClient to support socket-based DWDS functionality.
• Enhanced DevHandler with useWebSocketConnection flag to toggle between Chrome-based and WebSocket-based communication protocols.

related to #2605
- This setup currently works when launching from the terminal using the -d web-server flag. The app starts as expected, loads correctly, and hot reload functions properly.

WIP / Pending Implementation:

• Page refresh from IDEs still has some issues
• Missing test cases

Changes needed in Flutter Tools

// Change this:
bool get deviceIsDebuggable => device!.device is! WebServerDevice || debuggingOptions.startPaused;

// To this:
bool get deviceIsDebuggable => 
    device!.device is! WebServerDevice || 
    debuggingOptions.startPaused ||
    _useDwdsWebSocketConnection;

// And add this getter:
bool get _useDwdsWebSocketConnection {
  if (device?.devFS is WebDevFS) {
    return (device!.devFS! as WebDevFS).useDwdsWebSocketConnection;
  }
  return false;
}