fix: align DevTools host/network integration with upstream 1.2.0 mcp.js (#16)

Upstream chrome-devtools-mcp 1.2.0 reworked mcp.js: it exports Host and
NetworkManager and no longer expects consumers to install host bindings
themselves. The fork's overrideDevToolsGlobals() still ran the obsolete
DevTools.Host.InspectorFrontendHost.installInspectorFrontendHost(...) call and
carried a duplicate McpHostBindingAdapter (a stale copy of upstream's
McpHostBindings that even missed the real loadNetworkResource). Against the
1.2.0 bundle these crash with "Cannot read properties of undefined (reading
'InspectorFrontendHost')".

Drop the manual install and the duplicate adapter to match upstream 1.2.0,
which installs nothing here and relies on mcp.js. The follow-on
"NetworkManager undefined" error was a stale incremental build artifact,
fixed by a clean rebuild.

Co-authored-by: Claude <noreply@anthropic.com>

Author: triuzzi

src/devtools/DevtoolsUtils.ts

@@ -16,7 +16,6 @@ import type {
 } from '../third_party/index.js';
 
 import {PuppeteerDevToolsConnection} from './DevToolsConnectionAdapter.js';
-import {McpHostBindingAdapter} from './McpHostBindingAdapter.js';
 
 /**
  * A mock implementation of an issues manager that only implements the methods
@@ -30,9 +29,9 @@ export class FakeIssuesManager extends DevTools.Common.ObjectWrapper
 }
 
 export function overrideDevToolsGlobals(): void {
-  DevTools.Host.InspectorFrontendHost.installInspectorFrontendHost(
-    new McpHostBindingAdapter(),
-  );
+  // Host bindings are installed by upstream's mcp/mcp.js at import time
+  // (installInspectorFrontendHost(new McpHostBindings())). Since v1.2.0 the
+  // bundle self-installs them and no longer exports DevTools.Host for callers.
 
   // DevTools CDP errors can get noisy.
   DevTools.ProtocolClient.InspectorBackend.test.suppressRequestErrors = true;