Fire WS upstream event with 'ws' protocol, not 'http'

This matches the behaviour for exposed websocket event data elsewhere,
which uses ws/wss as the protocol consistently throughout.

Author: pimterry

src/rules/websockets/websocket-handlers.ts

@@ -396,7 +396,9 @@ export class PassThroughWebSocketHandler extends PassThroughWebSocketHandlerDefi
             const upstreamReq = (upstreamWebSocket as any as { _req: http.ClientRequest })._req;
             options.emitEventCallback('passthrough-websocket-connect', {
                 method: upstreamReq.method,
-                protocol: upstreamReq.protocol.replace(/:$/, ''),
+                protocol: upstreamReq.protocol
+                    .replace(/:$/, '')
+                    .replace(/^http/, 'ws'),
                 hostname: upstreamReq.host,
                 port: effectivePort.toString(),
                 path: upstreamReq.path,

test/integration/subscriptions/rule-events.spec.ts

@@ -342,7 +342,7 @@ describe("Rule event subscriptions", () => {
         const connectEvent = ruleEvents[0].eventData;
         expect(_.omit(connectEvent, 'rawHeaders')).to.deep.equal({
             method: 'GET',
-            protocol: 'http',
+            protocol: 'ws',
             hostname: 'localhost',
             // This reports the *modified* port, not the original:
             port: remoteServer.port.toString(),