fix: Chrome debug messages from iOS Runtime are not parsed correctly

During debug operation, iOS Runtime "talks" to Chrome DevTools. CLI stands as proxy between them and translates the messages. Due to Node.js socket implementation, some messages may come on chunks.
The format of each message is:
 - first 4 bytes contain the lenght of the message (in Big-Endian)
 - the next bytes are the actual message

Currently, the following behavior is observed:
 - when a full message is received, CLI sends it correctly to Chrome DevTools
 - when more than one message is received in the data, CLI sends only the first message to Chrome DevTools and disregards the other part
 - in case a split message is received, when the first part is only part of the first 4 bytes (part of the length), CLI fails with `Index out of Range` or `ERR_BUFFER_OUT_OF_BOUNDS` error (based on the inner state of the variables).

To fix this behavior, remove CLI's parsing and reuse the one from `ios-device-lib`.

Author: rosen-vladimirov

lib/device-sockets/ios/app-debug-socket-proxy-factory.ts

@@ -1,9 +1,9 @@
 import { EventEmitter } from "events";
 import { CONNECTION_ERROR_EVENT_NAME } from "../../constants";
-import { PacketStream } from "./packet-stream";
 import * as net from "net";
 import * as ws from "ws";
 import temp = require("temp");
+import { MessageUnpackStream } from "ios-device-lib";
 
 export class AppDebugSocketProxyFactory extends EventEmitter implements IAppDebugSocketProxyFactory {
 	private deviceWebServers: IDictionary<ws.Server> = {};
@@ -134,7 +134,7 @@ export class AppDebugSocketProxyFactory extends EventEmitter implements IAppDebu
 			const encoding = "utf16le";
 
 			const appDebugSocket: net.Socket = (<any>req)["__deviceSocket"];
-			const packets = new PacketStream();
+			const packets = new MessageUnpackStream();
 			appDebugSocket.pipe(packets);
 
 			packets.on("data", (buffer: Buffer) => {